[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 David Edmundson changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #31 from David Edmundson --- This is super old with no duplicates. Closing -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Christoph Feck changed: What|Removed |Added CC||zex...@gmail.com --- Comment #30 from Christoph Feck --- *** Bug 357631 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Steven Dobai changed: What|Removed |Added CC||sdtr...@protonmail.com --- Comment #29 from Steven Dobai --- Hello, These crashes happen with KDE neon too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Martin Gräßlin changed: What|Removed |Added CC||vincenzo.rom...@notorand.it --- Comment #28 from Martin Gräßlin --- *** Bug 368297 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Martin Gräßlin changed: What|Removed |Added CC||kdeb...@openaliasbox.org --- Comment #27 from Martin Gräßlin --- *** Bug 358966 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Martin Gräßlin changed: What|Removed |Added CC||xpr1...@mail.ru --- Comment #26 from Martin Gräßlin --- *** Bug 366385 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC||dutchgig...@gmail.com --- Comment #25 from Thomas Lübking --- *** Bug 363094 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #24 from Martin Gräßlin --- seems like we have a Qt 5.6 variant: https://bugs.kde.org/show_bug.cgi?id=361236 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC||davidsbo...@gmail.com --- Comment #23 from Thomas Lübking --- *** Bug 360323 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC||mike.cloa...@gmail.com --- Comment #22 from Thomas Lübking --- *** Bug 359064 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=358966 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #21 from Martin Gräßlin --- > if anything in QtQuick keeps/kept a dead engine around? I can add asserts to my local build. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #20 from Thomas Lübking --- Another thing I could think of because of the described pattern would be a problem w/ the Helper::ref/unref stuff - eg. if anything in QtQuick keeps/kept a dead engine around? Also what about operating on m_context /after/ the ::unref() call might have nuked engine and components and stuff? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #19 from Thomas Lübking --- Stupid question: FF is gtk3 on at least fedora. Do your FFs have a system titlebar? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #18 from Thomas Lübking --- No idea whether it's "fixed", but QML apparently gets a completely new data allocation mechanism: http://code.qt.io/cgit/qt/qtdeclarative.git/commit/src/qml/jsruntime/qv4stringobject.cpp?id=17a0c271e0ec606d15fc87dab23b2e3750c0e301 So we won't see *this* backtrace for sure on Qt 5.6 The problem is however the nullptr deref of the "string" member and that "merely" changed from "string = ic->engine->newString();" to "string = internalClass->engine->id_empty()->d();" - neither looks like there should ever be a nullptr. Maybe even the StringObject is nullptr. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #17 from Fabian Vogt --- I can reproduce it reliably by running while true; do (kwrite &); sleep 1; killall kwrite; done for a few minutes and then switching to an aurorae based theme. I'm also using Qt 5.5.1, so it might be fixed. The backtrace looks like: #25 0x7fffef9c6c70 in QQmlComponent::create(QQmlContext*) () at /usr/lib64/libQt5Qml.so.5 #26 0x7fffc42b5474 in () at /usr/lib64/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so #27 0x773278c0 in () at /usr/lib64/libkwin.so.5 #28 0x7721cba9 in () at /usr/lib64/libkwin.so.5 #29 0x77225c3b in () at /usr/lib64/libkwin.so.5 #30 0x7725b669 in () at /usr/lib64/libkwin.so.5 #31 0x773273ec in () at /usr/lib64/libkwin.so.5 #32 0x77329942 in () at /usr/lib64/libkwin.so.5 #33 0x75727e17 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5 #34 0x7720cef1 in KWin::Workspace::slotReconfigure() () at /usr/lib64/libkwin.so.5 with full debug info. Somehow gdb does not like kwin debugging, it does not show some symbols. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #16 from Martin Gräßlin --- > or it's fixed with Qt 5.6 which might be the case. The code in question changed significantly. The line QV4::Heap::StringObject::StringObject (this=, engine=0x2ac1220, val=...) at /usr/src/debug/qtdeclarative-opensource-src-5.5.1/src/qml/jsruntime/qv4stringobject.cpp:91 doesn't exist at all in 5.6 branch. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #15 from Martin Gräßlin --- For me the steps don't work. This could either mean there is more in it to reproduce it or it's fixed with Qt 5.6 (which I doubt). The backtraces never show from where in KWin the crash happens. If there is a chance to get the ?? sections in the backtrace filled, I have hope that we can fix it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #14 from a.skemb...@gmail.com --- (In reply to Martin Gräßlin from comment #13) > > 2) Open Firefox (via taskbar icon). > > you mean launching a firefox instance? Yes, It definitely triggers when the only and last activated window is the Virtualbox window, and I click on the taskbar icon of Firefox. I also have an icon in the "Desktop folder" widget, but I hardly use it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #13 from Martin Gräßlin --- > 2) Open Firefox (via taskbar icon). you mean launching a firefox instance? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 --- Comment #12 from a.skemb...@gmail.com --- I was informed I came across this bug, see https://forum.kde.org/viewtopic.php?f=111&t=130565 for the investigation that took place. In order to reproduce the bug consistently, using an aurorae-based theme and a dual monitor set up, I do the following: 1) Open a VM in Virtualbox in the second monitor and close Virtualbox Manager so that only the VM window is in the second monitor, maximized. 2) Open Firefox (via taskbar icon). Firefox will try to open on the main monitor and kwin will crash, with no DrKonqi to help out. Breeze decorations don't have this problem. The VM window needs to be the last active window before opening firefox, otherwise it's not triggered. I have attached a backtrace using gdb, but some symbols are missing, not sure from which packages. I am on OpenSUSE Tumbleweed, with KWin 5.5.3. Can reproduce consistently on Intel graphics laptop and ATI graphics desktop. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 a.skemb...@gmail.com changed: What|Removed |Added CC||a.skemb...@gmail.com --- Comment #11 from a.skemb...@gmail.com --- Created attachment 96847 --> https://bugs.kde.org/attachment.cgi?id=96847&action=edit Backtrace of KWin stopped process when crash happens -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC||kre...@email.com --- Comment #10 from Thomas Lübking --- *** Bug 349921 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC||l.bonn...@laposte.net --- Comment #9 from Thomas Lübking --- *** Bug 358204 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC||fab...@ritter-vogt.de --- Comment #8 from Thomas Lübking --- *** Bug 357742 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=357742 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject
https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC||eloy...@gmail.com --- Comment #7 from Thomas Lübking --- *** Bug 356480 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
