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

[REG 5.11-5.12.0] Android: crashes in QuickEventPoint::grabberItemEv

    XMLWordPrintable

Details

    • Android

    Description

      I am getting crash reports on Google Play after I compiled my Android app with Qt 5.12 that did not occur with Qt 5.11. Sorry that I cannot provide much information or a reproducible example. The only information I have are the stack traces on Google Play, which show only the function that the crash occured in:

      signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
      in _ZNK16QQuickEventPoint11grabberItemEv+23

      The bug seems to occur infrequently, but regularly. It never occured when the same app was still compiled with Qt 5.11. The bug might be related to QTBUG-65454. My app is QtQuick based, does dragging & dropping, and there are some event handlers that take some time if the CPU is already under load (so it could be timing-related).

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-72893 [REG: 5.11.3->5.12.0] Random crash in QQuickEventPoint::grabberItem

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-74008 Every 2-finger touchevent raises application crash

          • 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; Flaky tests; 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-67763 QtQuick PointerHandler's crashing in QQuickEventPoint::setGrabberItem when destroyed too fast

          • 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; Flaky tests; 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.
          • Open
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              srutledg Shawn Rutledge
              enz Markus Enzenberger
              Votes:
              4 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes