Bug 248220 - Kate crashes on closing Document
Summary: Kate crashes on closing Document
Status: RESOLVED DUPLICATE of bug 230426
Alias: None
Product: kate
Classification: Applications
Component: application (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-18 09:57 UTC by Ulrik Mikaelsson
Modified: 2010-10-23 16:47 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (8.84 KB, text/plain)
2010-10-15 23:49 UTC, Kai Krakow
Details
New crash information added by DrKonqi (8.84 KB, text/plain)
2010-10-15 23:49 UTC, Kai Krakow
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrik Mikaelsson 2010-08-18 09:57:09 UTC
Application: kwin (4.4.2 (KDE 4.4.2))
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic-pae i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
Kate crashes when closing document using Ctrl+W. It's does not crash at each document close, but if closing many documents in rapid succession, I'm sure to trigger the bug.

Documents were opened over sftp. 

The crash can be reproduced every time.

 -- Backtrace:
Application: Kwin (kwin), signal: Segmentation fault
[Current thread is 1 (Thread 0xb39c3720 (LWP 1753))]

Thread 2 (Thread 0xa70d3b70 (LWP 1754)):
#0  0xb4174e16 in *__GI_clock_gettime (clock_id=-1273524236, tp=0xa70d2fa8) at ../sysdeps/unix/clock_gettime.c:100
#1  0xb5e526fb in qt_gettime () at kernel/qcore_unix.cpp:111
#2  0xb5e57825 in QTimerInfoList::updateCurrentTime (this=0xa6701a34) at kernel/qeventdispatcher_unix.cpp:340
#3  0xb5e5786a in QTimerInfoList::timerWait (this=0xa6701a34, tm=...) at kernel/qeventdispatcher_unix.cpp:443
#4  0xb5e55818 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xa70d30bc) at kernel/qeventdispatcher_glib.cpp:136
#5  0xb5e558a5 in timerSourcePrepare (source=0x0, timeout=0xb4178ff4) at kernel/qeventdispatcher_glib.cpp:169
#6  0xb4299aca in g_main_context_prepare () from /lib/libglib-2.0.so.0
#7  0xb4299ee9 in ?? () from /lib/libglib-2.0.so.0
#8  0xb429a4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#9  0xb5e5560f in QEventDispatcherGlib::processEvents (this=0xa6700468, flags=...) at kernel/qeventdispatcher_glib.cpp:414
#10 0xb5e28059 in QEventLoop::processEvents (this=0xa70d3280, flags=) at kernel/qeventloop.cpp:149
#11 0xb5e284aa in QEventLoop::exec (this=0xa70d3280, flags=...) at kernel/qeventloop.cpp:201
#12 0xb5d245a8 in QThread::exec (this=0x9b02178) at thread/qthread.cpp:487
#13 0xb5e07c1b in QInotifyFileSystemWatcherEngine::run (this=0x9b02178) at io/qfilesystemwatcher_inotify.cpp:248
#14 0xb5d2732e in QThreadPrivate::start (arg=0x9b02178) at thread/qthread_unix.cpp:248
#15 0xb5cad96e in start_thread (arg=0xa70d3b70) at pthread_create.c:300
#16 0xb761da4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb39c3720 (LWP 1753)):
[KCrash Handler]
#6  0xb6e7bf73 in KWin::WindowMotionManager::manage (this=0x98b7c40, w=0x3) at ../../../kwin/lib/kwineffects.cpp:1169
#7  0xb207cbff in KWin::PresentWindowsEffect::setActive (this=0x98b7be8, active=true, closingTab=false) at ../../../kwin/effects/presentwindows/presentwindows.cpp:1559
#8  0xb207e06a in KWin::PresentWindowsEffect::toggleActiveAllDesktops (this=0x98b7be8, border=KWin::ElectricTopLeft) at ../../../kwin/effects/presentwindows/presentwindows.h:126
#9  KWin::PresentWindowsEffect::borderActivated (this=0x98b7be8, border=KWin::ElectricTopLeft) at ../../../kwin/effects/presentwindows/presentwindows.cpp:430
#10 0xb778d942 in KWin::EffectsHandlerImpl::borderActivated (this=0x987d178, border=KWin::ElectricTopLeft) at ../../kwin/effects.cpp:343
#11 0xb76edf5b in KWin::Workspace::checkElectricBorder (this=0x982a928, pos=..., now=1221403) at ../../kwin/workspace.cpp:2248
#12 0xb76ee3c2 in KWin::Workspace::electricBorderEvent (this=0x982a928, e=0xbfa0062c) at ../../kwin/workspace.cpp:2331
#13 0xb772ad05 in KWin::Workspace::workspaceEvent (this=0x982a928, e=0xbfa0062c) at ../../kwin/events.cpp:412
#14 0xb7703e32 in KWin::Application::x11EventFilter (this=0xbfa009d8, e=0xbfa0062c) at ../../kwin/main.cpp:361
#15 0xb616d660 in qt_x11EventFilter (ev=0xbfa0062c) at kernel/qapplication_x11.cpp:399
#16 0xb617ce90 in QApplication::x11ProcessEvent (this=0xbfa009d8, event=0xbfa0062c) at kernel/qapplication_x11.cpp:3231
#17 0xb61ad60a in x11EventSourceDispatch (s=0x97724f8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#18 0xb42965e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0xb429a2d8 in ?? () from /lib/libglib-2.0.so.0
#20 0xb429a4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#21 0xb5e555d5 in QEventDispatcherGlib::processEvents (this=0x9759de8, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#22 0xb61ad135 in QGuiEventDispatcherGlib::processEvents (this=0x9759de8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0xb5e28059 in QEventLoop::processEvents (this=0xbfa00924, flags=) at kernel/qeventloop.cpp:149
#24 0xb5e284aa in QEventLoop::exec (this=0xbfa00924, flags=...) at kernel/qeventloop.cpp:201
#25 0xb5e2c69f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#26 0xb60ed577 in QApplication::exec () at kernel/qapplication.cpp:3579
#27 0xb7705a00 in kdemain (argc=3, argv=0xbfa00be4) at ../../kwin/main.cpp:526
#28 0x0804860b in main (argc=3, argv=0xbfa00be4) at kwin_dummy.cpp:3

Reported using DrKonqi
Comment 1 Thomas Lübking 2010-08-18 14:17:39 UTC
The backtrace does not match the description
The trace shows a segfault in kwin while runnign the "present windows" (aka exposé) effect and is not related to kate (but might have happened in consequence)

Do you have to run the effect while closing kate docs to reproduce the crash?
Comment 2 Ulrik Mikaelsson 2010-08-18 15:55:00 UTC
Oh, that is interesting (didn't check the stacktrace myself, at work).

No, just ctrl+w in kate is enough to trigger this.
Comment 3 Thomas Lübking 2010-08-18 17:44:48 UTC
ok, if kate sefaults as well, you should ensure to file the proper backtrace there
Comment 4 Ulrik Mikaelsson 2010-08-18 19:30:58 UTC
Ok, just looked through the Stacktrace. The bug-reporting tool MUST have done something wrong. I could not see any flickering in KWin when this happened, only the Kate-application crashed, and could not see anything else. I just tried here at my home computer, with a local file open (not sftp:-uris this time).

Quickly hammering Ctrl+W a couple of times manages to trigger the problem here as well. Will try to get a stack trace out of it and post it shortly. (Problems with installing debug-symbols here for some reason.)
Comment 5 Ulrik Mikaelsson 2010-08-18 19:49:09 UTC
For some reason, DrKonqi failed to produce a usable backtrace, so here's what GDB think about the SEGFAULT instead;

#0  0xb6b5f919 in QUrl (this=0xbfffce5c, other=...) at io/qurl.cpp:4114
#1  0xb7258ea9 in KUrl::KUrl(KUrl const&) () from /usr/lib/libkdecore.so.5
#2  0xb63a0d2f in KParts::ReadOnlyPart::url() const () from /usr/lib/libkparts.so.4
#3  0xb712bc24 in KateDocManager::data (this=0x8140d08, index=..., role=35) at ../../../kate/app/katedocmanager.cpp:133
#4  0xb7165654 in KateViewDocumentProxyModel::data (this=0x8265e60, index=..., role=35) at ../../../kate/app/kateviewdocumentproxymodel.cpp:325
#5  0xb716760c in KateViewDocumentProxyModel::sort (this=0x8265e60) at ../../../kate/app/kateviewdocumentproxymodel.cpp:637
#6  0xb7168b38 in KateViewDocumentProxyModel::opened (this=0x8265e60, index=...) at ../../../kate/app/kateviewdocumentproxymodel.cpp:216
#7  0xb7137554 in KateMainWindow::slotWindowActivated (this=0x8228450) at ../../../kate/app/katemainwindow.cpp:566
#8  0xb713cc65 in KateMainWindow::qt_metacall (this=0x8228450, _c=QMetaObject::InvokeMetaMethod, _id=59, _a=0xbfffd2ac) at ./katemainwindow.moc:181
#9  0xb6bb6c9a in QMetaObject::metacall (object=0x8228450, cl=33, idx=59, argv=0xbfffd2ac) at kernel/qmetaobject.cpp:237
#10 0xb6bc53d5 in QMetaObject::activate (sender=0x823c1b0, m=0xb717c4c4, local_signal_index=1, argv=0x0) at kernel/qobject.cpp:3293
#11 0xb713fec7 in KateViewManager::viewChanged (this=0x823c1b0) at ./kateviewmanager.moc:164
#12 0xb714244b in KateViewManager::activateView (this=0x823c1b0, view=0x88bec48) at ../../../kate/app/kateviewmanager.cpp:469
#13 0xb7143301 in KateViewManager::createView (this=0x823c1b0, doc=0x8aac6a8) at ../../../kate/app/kateviewmanager.cpp:308
#14 0xb71448dc in KateViewManager::qt_metacall (this=0x823c1b0, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xbfffd4b8) at ./kateviewmanager.moc:138
#15 0xb6bb6c9a in QMetaObject::metacall (object=0x823c1b0, cl=33, idx=45, argv=0xbfffd4b8) at kernel/qmetaobject.cpp:237
#16 0xb6bc53d5 in QMetaObject::activate (sender=0x8140d08, m=0xb717b6f4, local_signal_index=2, argv=0xbfffd4b8) at kernel/qobject.cpp:3293

#17 0xb7125d43 in KateDocManager::documentDeleted (this=0x8140d08, _t1=0x8965190) at ./katedocmanager.moc:138
#18 0xb7127379 in KateDocManager::deleteDoc (this=0x8140d08, doc=0x8965190) at ../../../kate/app/katedocmanager.cpp:218
#19 0xb712c499 in KateDocManager::closeDocument (this=0x8140d08, doc=0x8965190, closeUrl=true) at ../../../kate/app/katedocmanager.cpp:366
#20 0xb713ffb8 in KateViewManager::slotDocumentClose (this=0x823c1b0, document=0x8965190) at ../../../kate/app/kateviewmanager.cpp:205
#21 0xb7142fd5 in KateViewManager::slotDocumentClose (this=0x823c1b0) at ../../../kate/app/kateviewmanager.cpp:214
#22 0xb7144820 in KateViewManager::qt_metacall (this=0x823c1b0, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfffd968) at ./kateviewmanager.moc:130
#23 0xb6bb6c9a in QMetaObject::metacall (object=0x823c1b0, cl=33, idx=37, argv=0xbfffd968) at kernel/qmetaobject.cpp:237
#24 0xb6bc53d5 in QMetaObject::activate (sender=0x82d0c58, m=0xb7e38d58, local_signal_index=1, argv=0xbfffd968) at kernel/qobject.cpp:3293
#25 0xb7509bd9 in QAction::triggered (this=0x82d0c58, _t1=false) at .moc/release-shared/moc_qaction.cpp:263
#26 0xb750bdcc in QAction::activate (this=0x82d0c58, event=QAction::Trigger) at kernel/qaction.cpp:1255
#27 0xb750d698 in QAction::event (this=0xbfffce5c, e=0x3c) at kernel/qaction.cpp:1181
#28 0xb6e34d63 in KAction::event(QEvent*) () from /usr/lib/libkdeui.so.5
#29 0xb75104dc in QApplicationPrivate::notify_helper (this=0x8071840, receiver=0xbfffde88, e=0xbfffde88) at kernel/qapplication.cpp:4300
#30 0xb751705e in QApplication::notify (this=0xbfffedb4, receiver=0x82d0c58, e=0xbfffde88) at kernel/qapplication.cpp:3704
#31 0xb6f20f2a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#32 0xb6bb1a3b in QCoreApplication::notifyInternal (this=0xbfffedb4, receiver=0x82d0c58, event=0xbfffde88) at kernel/qcoreapplication.cpp:704
#33 0xb755234d in QCoreApplication::sendEvent (this=0x80718ec, e=0xbfffe304) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#34 QShortcutMap::dispatchEvent (this=0x80718ec, e=0xbfffe304) at kernel/qshortcutmap.cpp:879
#35 0xb755415e in QShortcutMap::tryShortcutEvent (this=0x80718ec, o=0x852a120, e=0xbfffe304) at kernel/qshortcutmap.cpp:364
#36 0xb7518e43 in QApplication::notify (this=0xbfffedb4, receiver=0x852a120, e=0xbfffe304) at kernel/qapplication.cpp:3746
#37 0xb6f20f2a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#38 0xb6bb1a3b in QCoreApplication::notifyInternal (this=0xbfffedb4, receiver=0x852a120, event=0xbfffe304) at kernel/qcoreapplication.cpp:704
#39 0xb75112be in QCoreApplication::sendSpontaneousEvent (receiver=0x852a120, event=0xbfffce5c)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#40 qt_sendSpontaneousEvent (receiver=0x852a120, event=0xbfffce5c) at kernel/qapplication.cpp:5279
#41 0xb75cad90 in QKeyMapper::sendKeyEvent (keyWidget=0x852a120, grab=false, type=QEvent::KeyPress, code=87, modifiers=..., text=..., 
    autorepeat=<value optimised out>, count=<value optimised out>, nativeScanCode=25, nativeVirtualKey=119, nativeModifiers=20)
    at kernel/qkeymapper_x11.cpp:1861
#42 0xb75cd2f5 in QKeyMapperPrivate::translateKeyEvent (this=0x809b558, keyWidget=0x852a120, event=0xbfffe9cc, grab=60)
    at kernel/qkeymapper_x11.cpp:1831
#43 0xb75a0757 in QApplication::x11ProcessEvent (this=0xbfffedb4, event=0xbfffe9cc) at kernel/qapplication_x11.cpp:3394
#44 0xb75d060a in x11EventSourceDispatch (s=0x80747f8, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#45 0xb68645e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#46 0xb68682d8 in ?? () from /lib/libglib-2.0.so.0
#47 0xb68684b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#48 0xb6bdd5d5 in QEventDispatcherGlib::processEvents (this=0x80544a0, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#49 0xb75d0135 in QGuiEventDispatcherGlib::processEvents (this=0x80544a0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#50 0xb6bb0059 in QEventLoop::processEvents (this=0xbfffecc4, flags=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qeventloop.cpp:149
#51 0xb6bb04aa in QEventLoop::exec (this=0xbfffecc4, flags=...) at kernel/qeventloop.cpp:201
#52 0xb6bb469f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#53 0xb7510577 in QApplication::exec () at kernel/qapplication.cpp:3579
---Type <return> to continue, or q <return> to quit---
#54 0xb7fdaa65 in kdemain (argc=1, argv=0xbffff454) at ../../../kate/app/katemain.cpp:377
#55 0x080485fb in main (argc=1, argv=0xbffff454) at kate_dummy.cpp:3
Comment 6 Thomas Lübking 2010-08-18 20:40:06 UTC
Ok, thanks, re-assigning to kate
Comment 7 Kai Krakow 2010-10-15 23:49:12 UTC
Created attachment 52554 [details]
New crash information added by DrKonqi

This is really an annoying bug. Almost always when I try to close a document, kate just crashes - loosing all unsaved data! (and some settings, too)
Comment 8 Kai Krakow 2010-10-15 23:49:13 UTC
Created attachment 52555 [details]
New crash information added by DrKonqi

This is really an annoying bug. Almost always when I try to close a document, kate just crashes - loosing all unsaved data! (and some settings, too)
Comment 9 Kai Krakow 2010-10-15 23:52:12 UTC
Sorry for the double post, drkonqi told me "timeout while communicating with bugs.kde.org" :-(
Comment 10 Christoph Feck 2010-10-23 16:47:51 UTC

*** This bug has been marked as a duplicate of bug 230426 ***