Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-91736

Ensure Qt containers behave correctly when empty

    XMLWordPrintable

Details

    • 13
    • Qt6_Foundation_Sprint 37, Qt6_Foundation_Sprint 38, Qt6_Foundation_Sprint 39

    Description

      Given recent findings like QTBUG-89687 and QTBUG-91704 it seems essential to verify that containers behave correctly in an edge case of being empty.
      Thus, we need a comprehensive test coverage for such scenarios.
      Containers list (may not be complete):

      • QList, QString, QByteArray
      • QVarLengthArray
      • QStack, QQueue
      • QSet, QMap, QMultiMap
      • QHash, QMultiHash

      The following should be tested:
      1. At least, no operation on an empty container causes a crash or UB (see related bug reports for an example)
      2. At most, no operation on an empty container causes it to allocate memory - this is a soft requirement as some operations could detach straight away and we accept it (e.g. having an explicit if-statement would harm the performance)

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-89687 QMultiHash::equal_range crashes when called in a const member function

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-91704 QMultiHash::count(key) crashes on empty container

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              ivan.solovev Ivan Solovev
              agolubev Andrei Golubev
              Vladimir Minenko Vladimir Minenko
              Alex Blasche Alex Blasche
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes