Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-2981

Importing TBX with invalid XML leads to high CPU usage

    XMLWordPrintable

Details

    • Critical
    • On importing a TBX file with invalid XML the import process was caught in an endless loop. This is fixed and the import stops now with an error message.
    • -

    Description

      Problem

      If the tbx is invalid and it is imported, instead of skipping the invalid part or throwing an exception, the import is stuck and the termcollection is in importing state.

      To reproduce this, use the tbx file in next cloud with the name as the issue.

      Attachments

        Activity

          People

            tlauria Thomas Lauria
            aleksandar Aleksandar Mitrev
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: