Application: kate (23.08.5) Qt Version: 5.15.12 Frameworks Version: 5.115.0 Operating System: Linux 6.7.4-arch1-1 x86_64 Windowing System: X11 Distribution: Arch Linux DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: Kate crashed when I switched from another window using Alt+Tab, triggered Quick Open using Ctrl+Alt+O, and started typing. I have not been able to reproduce this crash again. This was on X11, so it does not seem to be a duplicate of https://bugs.kde.org/show_bug.cgi?id=471791 The crash does not seem to be reproducible. -- Backtrace: Application: கேட் (kate), signal: Segmentation fault Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>} [KCrash Handler] #6 0x00007a11de9c049a in KateQuickOpenModel::refresh (this=0x5f1e46832f50, mainWindow=<optimized out>) at /usr/src/debug/kate/kate-23.08.5/apps/lib/quickopen/katequickopenmodel.cpp:137 #7 0x00007a11de9c0d2c in KateQuickOpen::updateState (this=0x7ffd79c095d0) at /usr/src/debug/kate/kate-23.08.5/apps/lib/quickopen/katequickopen.cpp:379 #8 0x00007a11de9e79f4 in KateQuickOpen::KateQuickOpen (mainWindow=<optimized out>, this=0x7ffd79c095d0) at /usr/src/debug/kate/kate-23.08.5/apps/lib/quickopen/katequickopen.cpp:336 #9 KateMainWindow::slotQuickOpen (this=0x5f1e45854490) at /usr/src/debug/kate/kate-23.08.5/apps/lib/katemainwindow.cpp:1489 #10 0x00007a11dd4c8e27 in QtPrivate::QSlotObjectBase::call (a=0x7ffd79c09760, r=<optimized out>, this=0x5f1e458f59a0, this=<optimized out>, r=<optimized out>, a=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #11 doActivate<false> (sender=0x5f1e44a2fdd0, signal_index=4, argv=0x7ffd79c09760) at kernel/qobject.cpp:3925 #12 0x00007a11de14abb7 in QAction::triggered (this=this@entry=0x5f1e44a2fdd0, _t1=<optimized out>) at .moc/moc_qaction.cpp:376 #13 0x00007a11de15060b in QAction::activate (this=0x5f1e44a2fdd0, event=<optimized out>) at kernel/qaction.cpp:1161 #14 0x00007a11de1506de in QAction::event (e=<optimized out>, this=<optimized out>) at kernel/qaction.cpp:1086 #15 QAction::event (this=<optimized out>, e=<optimized out>) at kernel/qaction.cpp:1075 #16 0x00007a11de1578ff in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x5f1e44a2fdd0, e=0x7ffd79c098f0) at kernel/qapplication.cpp:3640 #17 0x00007a11dd493ef8 in QCoreApplication::notifyInternal2 (receiver=0x5f1e44a2fdd0, event=0x7ffd79c098f0) at kernel/qcoreapplication.cpp:1064 #18 0x00007a11dd493f63 in QCoreApplication::sendEvent (receiver=<optimized out>, event=<optimized out>) at kernel/qcoreapplication.cpp:1462 #19 0x00007a11dd967026 in QShortcutMap::dispatchEvent (this=this@entry=0x5f1e4487ae58, e=e@entry=0x7ffd79c099b0) at kernel/qshortcutmap.cpp:675 #20 0x00007a11dd967415 in QShortcutMap::tryShortcut (this=0x5f1e4487ae58, e=0x7ffd79c099b0) at kernel/qshortcutmap.cpp:343 #21 0x00007a11dd91be08 in QWindowSystemInterface::handleShortcutEvent (window=<optimized out>, timestamp=82160172, keyCode=79, modifiers=..., nativeScanCode=32, nativeVirtualKey=111, nativeModifiers=12, text=..., autorepeat=false, count=1) at kernel/qwindowsysteminterface.cpp:477 #22 0x00007a11dd935522 in QGuiApplicationPrivate::processKeyEvent (e=0x7ffd79c09b50) at kernel/qguiapplication.cpp:2398 #23 0x00007a11d7a6e965 in QIBusPlatformInputContext::filterEventFinished (this=<optimized out>, call=0x5f1e480b79b0) at /usr/src/debug/qt5-base/qtbase/src/plugins/platforminputcontexts/ibus/qibusplatforminputcontext.cpp:517 #24 0x00007a11dd4c8e27 in QtPrivate::QSlotObjectBase::call (a=0x7ffd79c09ce0, r=<optimized out>, this=0x5f1e48124e90, this=<optimized out>, r=<optimized out>, a=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #25 doActivate<false> (sender=0x5f1e480b79b0, signal_index=3, argv=0x7ffd79c09ce0) at kernel/qobject.cpp:3925 #26 0x00007a11de7b1ad4 in QDBusPendingCallWatcher::finished (this=<optimized out>, _t1=<optimized out>) at .moc/moc_qdbuspendingcall.cpp:158 #27 0x00007a11dd4bb964 in QObject::event (this=0x5f1e480b79b0, e=0x5f1e477a1740) at kernel/qobject.cpp:1347 #28 0x00007a11de1578ff in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x5f1e480b79b0, e=0x5f1e477a1740) at kernel/qapplication.cpp:3640 #29 0x00007a11dd493ef8 in QCoreApplication::notifyInternal2 (receiver=0x5f1e480b79b0, event=0x5f1e477a1740) at kernel/qcoreapplication.cpp:1064 #30 0x00007a11dd498e5b in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5f1e44859580) at kernel/qcoreapplication.cpp:1821 #31 0x00007a11dd4deec8 in postEventSourceDispatch (s=0x5f1e449cb2b0) at kernel/qeventdispatcher_glib.cpp:277 #32 0x00007a11dad0df69 in g_main_dispatch (context=0x7a11d0000ec0) at ../glib/glib/gmain.c:3476 #33 0x00007a11dad6c3a7 in g_main_context_dispatch_unlocked (context=0x7a11d0000ec0) at ../glib/glib/gmain.c:4284 #34 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x7a11d0000ec0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4349 #35 0x00007a11dad0c162 in g_main_context_iteration (context=0x7a11d0000ec0, may_block=1) at ../glib/glib/gmain.c:4414 #36 0x00007a11dd4e2d0c in QEventDispatcherGlib::processEvents (this=0x5f1e449d54b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #37 0x00007a11dd492c04 in QEventLoop::exec (this=this@entry=0x7ffd79c0a140, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #38 0x00007a11dd4940a3 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #39 0x00007a11dd92bef2 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1870 #40 0x00007a11de155cda in QApplication::exec () at kernel/qapplication.cpp:2832 #41 0x00005f1e445a660e in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kate/kate-23.08.5/apps/kate/main.cpp:609 [Inferior 1 (process 298600) detached] Reported using DrKonqi
This is crashing because of a stale pointer in view manager. This has been seen before but so far we have no idea why this happens Some questions that might help: - Did you use splits in the session that crashed? - Did you use tab drag and drop feature? - How do you normally close a tab/document?
(In reply to Waqar Ahmed from comment #1) > This is crashing because of a stale pointer in view manager. This has been > seen before but so far we have no idea why this happens > > Some questions that might help: > > - Did you use splits in the session that crashed? > - Did you use tab drag and drop feature? > - How do you normally close a tab/document? I was using split view (two splits side-by-side). I usually don't drag/drop tabs (at best, I occasionally right-click on a tab and use the option to detach it from the window. Usually I just close the entire window when I am done by middle-clicking on the titlebar.
Could you retry this with the new 24.04 release?
(In reply to Christoph Cullmann from comment #3) > Could you retry this with the new 24.04 release? Do you mean 24.02? I just updated to it; I will comment on this report if the crash happens again (hasn't happened so far, but it wasn't that common even earlier).
(In reply to Kishore Gopalakrishnan from comment #4) > (In reply to Christoph Cullmann from comment #3) > > Could you retry this with the new 24.04 release? > > Do you mean 24.02? I just updated to it; I will comment on this report if > the crash happens again (hasn't happened so far, but it wasn't that common > even earlier). Yes, I meant 24.02.