Details
-
Bug
-
Resolution: Cannot Reproduce
-
P3: Somewhat important
-
5.6.2
-
Android 6.0
Description
If an Android application quickly receives onPause/onResume, etc... the slots connected to applicationStateChanged can be triggered out of order, where the parameter passed in does not match the value retrieved from applicationState().
In the attached example the Android activity was modified to call onPause/onResume back to back for ease of demonstration.
Attachments
For Gerrit Dashboard: QTBUG-58759 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
267268,1 | Fix app processing state changes out of order | dev | qt/qtbase | Status: NEW | 0 | 0 |