Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
5.9.1
-
Linux, ARM
Description
In particular scenario in QML application we often catch a crash (not every time).
Scenario includes:
- using Loader QML component to load and unload our QML views
- our QML views contain animations:
a. SequentialAnimation: NumberAnimation, PauseAnimation { duration: 400 }, NumberAnimation
b. NumberAnimation
c. ParallelAnimation (with 2 PropertyAnimations)
This is a proprietary software, so we could not share the code. Maybe later we will be managed to prepare some demo application which reproduces the issue, but we hope that currently provided information will be enough to start investigation on your side.
Issue and stack trace are quite similar to the crash described in QTBUG-43210.
Stack trace:
Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000007f7ba9e2a4 in QMetaObject::activate(QObject, int, int, void*) () from /usr/lib/libQt5Core.so.5 [Current thread is 1 (LWP 1256)] (gdb) bt full #0 0x0000007f7ba9e2a4 in QMetaObject::activate(QObject, int, int, void*) () from /usr/lib/libQt5Core.so.5 No symbol table info available. #1 0x0000007f7c00cf58 in QAbstractAnimationJob::stateChanged(QAbstractAnimation Job::State, QAbstractAnimationJob::State) () from /usr/lib/libQt5Qml.so.5 No symbol table info available. #2 0x0000007f7c00d880 in QAbstractAnimationJob::setState(QAbstractAnimationJob: :State) () from /usr/lib/libQt5Qml.so.5 No symbol table info available. #3 0x0000007f7c00dbac in QAbstractAnimationJob::setCurrentTime(int) () from /usr/lib/libQt5Qml.so.5 No symbol table info available. #4 0x0000007f7c00ddb4 in QQmlAnimationTimer::updateAnimationsTime(long long) () from /usr/lib/libQt5Qml.so.5 No symbol table info available. Backtrace stopped: previous frame identical to this frame (corrupt stack?)
Attachments
Issue Links
- relates to
-
QTBUG-43210 Qt Quick crashes in QAbstractAnimationJob::stateChanged
-
- Closed
-