https://bugs.kde.org/show_bug.cgi?id=491699
--- Comment #39 from Adam Fontenot <[email protected]> --- (In reply to Martin Bednar from comment #37) > you have a trace? I'd be curious if in 6.10 it's more sensical, because in > 6.9 it has all the hallmarks of compilation dependent memory overwrite... > the infamous heisenbug Unfortunately, I unthinkingly stripped the debug symbols when I rebuilt Qt, but what I did get looked a lot like your backtrace. I'm trying again, this time including both the QTBUG-141105 fix and also this one: https://codereview.qt-project.org/c/qt/qtdeclarative/+/688387 The latter was reported recently on the Qt bug as part of another way to trigger the same crash. With *both* cherry-picked to 6.10, I haven't been able to reproduce the issue so far. Curious if you're able to, since you report being able to reproduce 100% of the time. -- You are receiving this mail because: You are watching all bug changes.
