https://bugs.kde.org/show_bug.cgi?id=314213
Jonathan Verner <jonathan.ver...@matfyz.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED CC| |jonathan.ver...@matfyz.cz --- Comment #17 from Jonathan Verner <jonathan.ver...@matfyz.cz> --- Hmm, I hit this crash again today. The (relevant part of the) back-trace is as follows: #0 Python::PythonDeclarationCompletionItem::data(QModelIndex const&, int, KDevelop::CodeCompletionModel const*) const (this=0x7ffed4ca3110, index=..., role=258, model=0x55555af291d0) at kdev-python/codecompletion/items/declaration.cpp:92 #1 in KDevelop::CodeCompletionModel::data(QModelIndex const&, int) const (this=0x55555af291d0, index=..., role=258) at kdevelop/kdevplatform/language/codecompletion/codecompletionmodel.cpp:378 #2 in KateCompletionModel::contextMatchQuality(QPair<KTextEditor::CodeCompletionModel*, QModelIndex> const&) const () at /usr/lib/x86_64-linux-gnu/libKF5TextEditor.so.5 The code crashes because `model->completionContext()->duContext()` is null at that point (although non-nullness was checked previously on line 79 of kdev-python/codecompletion/items/declaration.cpp, per the fix by @Sven in f5353859631f12561) Probably a DUChainReader lock around the switch statement would help? -- You are receiving this mail because: You are watching all bug changes.