https://bugs.kde.org/show_bug.cgi?id=404227
Jan Kundrát <j...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|REPORTED |RESOLVED
--- Comment #1 from Jan Kundrát <j...@kde.org> ---
Thanks for reporting this and thanks for providing a usable backtrace, Jonáš.
Here's a brief analysis of what might be happening, but I do not currently have
time to dig into this deeper.
Rapid network reconnects result in invalidating subtrees of our
QAbstractItemModel subclass. This is not a problem, the code "should be
designed" with this in mind. There are plenty of Q_ASSERT macros which enforce
this assumption, guaranteeing that the app crashes reasonably cleanly whenever
there's a code bug (i.e., when the code assumes that, say, a given message is
still available in the model tree, while it got "invalidated" by a rescan upon
a network reconnect). The problem is that these assertions are removed in
release builds. Unless you've built with USE=debug, you do not have these
assertions, and the code no longer dies "soon enough". It might keep working
over invalidated QModelIndex instances for a short while, hitting a segfault
when the memory has been finally repurposed and/or corrupted.
If this is all correct, then this sounds like a duplicate of
https://bugs.kde.org/show_bug.cgi?id=392800 . Looking at the date of filing and
its history, it's indeed rather hard to reproduce that one :(.
*** This bug has been marked as a duplicate of bug 392800 ***
--
You are receiving this mail because:
You are watching all bug changes.
