Application: kate (20.03.70) (Compiled from sources) Qt Version: 5.14.0 Frameworks Version: 5.66.0 Operating System: Linux 5.4.8-arch1-1 x86_64 Distribution: Arch Linux -- Information about the crash: Editing some non-exciting regular QML. I had a crash, hope it's useful. I then restarted and continued editing the same file and it was all fine. Qt 5.14.1 branch The crash does not seem to be reproducible. -- Backtrace (Reduced): #6 0x00007f70651210c2 in QV4::Chunk::testBit (bitmap=0x7f7054050318, index=200) at ../../include/QtQml/5.14.0/QtQml/private/../../../../../../../qt5/qtdeclarative/src/qml/memory/qv4mmdefs_p.h:142 #7 0x00007f70651214d6 in QV4::Heap::Base::inUse (this=0x7f7054051900) at ../../include/QtQml/5.14.0/QtQml/private/../../../../../../../qt5/qtdeclarative/src/qml/memory/qv4heap_p.h:127 #8 0x00007f70651217da in QV4::Managed::inUse (this=0x7f7054051908) at /home/david/projects/qt5/qtdeclarative/src/qml/jsruntime/qv4managed_p.h:177 #9 0x00007f706511f331 in QV4::MemoryManager::collectFromJSStack (this=0x56059d4cdd80, markStack=0x7fffd9d17170) at /home/david/projects/qt5/qtdeclarative/src/qml/memory/qv4mm.cpp:1219 #10 0x00007f706511d093 in QV4::MemoryManager::collectRoots (this=0x56059d4cdd80, markStack=0x7fffd9d17170) at /home/david/projects/qt5/qtdeclarative/src/qml/memory/qv4mm.cpp:873 Reported using DrKonqi
Created attachment 125197 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
For me that looks like the JS GC is broken :/
If you can reproduce that, consider reporting it upstream. I found some old report: https://bugreports.qt.io/browse/QTBUG-69525
Without a way to reproduce, guess we don't need to ping the Qt people.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
Created attachment 129025 [details] New crash information added by DrKonqi kate (20.04.0) using Qt 5.14.1 - What I was doing when the application crashed: I've edited regular javascript file. Nothing special, never happen to me before. After restart all works correctly. -- Backtrace (Reduced): #7 QV4::Heap::Base::inUse (this=0x7f7d013bc820) at ../../include/QtQml/5.14.1/QtQml/private/../../../../../src/qml/memory/qv4mmdefs_p.h:142 #8 QV4::Managed::inUse (this=0x7f7d013bc830) at jsruntime/qv4managed_p.h:177 #9 QV4::MemoryManager::collectFromJSStack (this=<optimized out>, markStack=0x7ffc341a73a0) at memory/qv4mm.cpp:1219 #10 0x00007f7d58b12189 in QV4::MemoryManager::collectRoots (this=0x5621a642a260, markStack=0x7ffc341a73a0) at memory/qv4mm.cpp:873 #11 0x00007f7d58b123bd in QV4::MemoryManager::mark (this=this@entry=0x5621a642a260) at memory/qv4mm.cpp:917