https://bugs.kde.org/show_bug.cgi?id=428769
--- Comment #4 from Jürgen Thomann <juergen_thom...@linfre.de> --- Created attachment 138075 --> https://bugs.kde.org/attachment.cgi?id=138075&action=edit New crash information added by DrKonqi amarok (2.9.71) using Qt 5.15.2 Current Backtrace Seems like the Syntaxhiglighter sets the document during deletion that triggers a signal which causes access to already deleted objects when checking for changes in the objects of the UI -- Backtrace (Reduced): #6 QFragmentMapData<QTextFragmentData>::length(unsigned int) const (this=<optimized out>, this=<optimized out>, field=0) at ../../include/QtGui/5.15.2/QtGui/private/../../../../../src/gui/text/qfragmentmap_p.h:147 #7 QFragmentMap<QTextFragmentData>::length(unsigned int) const (field=0, this=<optimized out>) at ../../include/QtGui/5.15.2/QtGui/private/../../../../../src/gui/text/qfragmentmap_p.h:822 #8 QTextDocumentPrivate::length() const (this=<optimized out>) at text/qtextdocument_p.h:220 #9 QTextDocumentPrivate::plainText() const (this=0x558b83e85dc0) at text/qtextdocument_p.cpp:1339 #10 0x00007f1ef8e887b2 in QTextDocument::toPlainText() const (this=<optimized out>) at text/qtextdocument.cpp:1207 -- You are receiving this mail because: You are watching all bug changes.
