subject:"\[kwin\] \[Bug 351839\] segfault in QV4\:\:ExecutionEngine\:\:newStringObject"

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2022-02-23 Thread David Edmundson

https://bugs.kde.org/show_bug.cgi?id=351839 David Edmundson changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2019-12-02 Thread Nate Graham

https://bugs.kde.org/show_bug.cgi?id=351839 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2017-04-13 Thread Simon Andric

https://bugs.kde.org/show_bug.cgi?id=351839 Simon Andric changed: What|Removed |Added CC||simonandr...@gmail.com

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2017-01-04 Thread Christoph Feck

https://bugs.kde.org/show_bug.cgi?id=351839 Christoph Feck changed: What|Removed |Added CC||zex...@gmail.com --- Comment

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-10-25 Thread Steven Dobai via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=351839 Steven Dobai changed: What|Removed |Added CC||sdtr...@protonmail.com

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-09-09 Thread Martin Gräßlin via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=351839 Martin Gräßlin changed: What|Removed |Added CC|

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-09-02 Thread Martin Gräßlin via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=351839 Martin Gräßlin changed: What|Removed |Added CC||kdeb...@openaliasbox.org

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-08-04 Thread Martin Gräßlin via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=351839 Martin Gräßlin changed: What|Removed |Added CC||xpr1...@mail.ru ---

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-04-01 Thread Martin Gräßlin via KDE Bugzilla

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

2016-03-09 Thread Thomas Lübking via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC|

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-02-06 Thread Thomas Lübking via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added CC|

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-02-03 Thread Thomas Lübking via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=351839 Thomas Lübking changed: What|Removed |Added See Also|

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-26 Thread via KDE Bugzilla

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=130565 for the investigation that took place. In order to reproduce the bug consistently, using an aurorae-based theme

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-26 Thread via KDE Bugzilla

https://bugs.kde.org/show_bug.cgi?id=351839 a.skemb...@gmail.com changed: What|Removed |Added CC||a.skemb...@gmail.com --- Comment #11

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-26 Thread via KDE Bugzilla

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-26 Thread Martin Gräßlin via KDE Bugzilla

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-26 Thread Martin Gräßlin via KDE Bugzilla

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-26 Thread Thomas Lübking via KDE Bugzilla

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-26 Thread Martin Gräßlin via KDE Bugzilla

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

2016-01-26 Thread Fabian Vogt via KDE Bugzilla

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

[kwin] [Bug 351839] segfault in QV4::ExecutionEngine::newStringObject

2016-01-26 Thread Thomas Lübking via KDE Bugzilla

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

2016-01-26 Thread Thomas Lübking via KDE Bugzilla

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: