Bug 151759 - crash when closing progress dialog
Summary: crash when closing progress dialog
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-02 19:09 UTC by Martin Koller
Modified: 2009-04-22 16:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Koller 2007-11-02 19:09:02 UTC
Version:           unknown (using KDE 3.95.00 (KDE 4.0 Beta4))
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.18.8-0.7-default

I did a right-click inside konqueror on a link and selected
open with -> kate
Kate opened and also a progress dialog (which stayed empty; no source, no target). So I clciked cancel and kate crashed:
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1239791920 (LWP 30922)]
[KCrash handler]
#9  0xb7e39e4f in KJob::kill (this=0x82df888, verbosity=KJob::Quietly)
    at /home/KDE4/source/kdelibs/kdecore/jobs/kjob.cpp:106
#10 0xb7cdc574 in KParts::ReadOnlyPart::abortLoad (this=0x8125c38)
    at /home/KDE4/source/kdelibs/kparts/part.cpp:596
#11 0xb7cde55b in KParts::ReadOnlyPart::closeUrl (this=0x8125c38)
    at /home/KDE4/source/kdelibs/kparts/part.cpp:605
#12 0xb7ce0040 in ~ReadOnlyPart (this=0x8125c38, __vtt_parm=0xb490518c)
    at /home/KDE4/source/kdelibs/kparts/part.cpp:454
#13 0xb7ce0191 in ~ReadWritePart (this=0x8125c38, __vtt_parm=0xb4905188)
    at /home/KDE4/source/kdelibs/kparts/part.cpp:717
#14 0xb67273b5 in ~Document (this=0x8125c38, __vtt_parm=0xb4905184)
    at /home/KDE4/source/kdelibs/interfaces/ktexteditor/ktexteditor.cpp:104
#15 0xb47c4f2b in ~KateDocument (this=0x8125c38)
    at /home/KDE4/source/kdelibs/kate/document/katedocument.cpp:373
#16 0xb6f91031 in QObjectPrivate::deleteChildren ()
   from /usr/lib/libQtCore.so.4
#17 0xb6f9558e in QObject::~QObject () from /usr/lib/libQtCore.so.4
#18 0xb6f7c27f in QAbstractItemModel::~QAbstractItemModel ()
   from /usr/lib/libQtCore.so.4
#19 0xb6ce1038 in QStandardItemModel::~QStandardItemModel ()
   from /usr/lib/libQtGui.so.4
#20 0xb7d32688 in ~KateDocManager (this=0x8121420)
    at /home/KDE4/source/kdesdk/kate/app/katedocmanager.cpp:103
#21 0xb7d2624f in ~KateApp (this=0xbfc3d6bc)
    at /home/KDE4/source/kdesdk/kate/app/kateapp.cpp:95
#22 0xb7f7fac6 in kdemain (argc=2, argv=0xbfc3dc64)
    at /home/KDE4/source/kdesdk/kate/app/katemain.cpp:271
#23 0x080487e2 in main (argc=-1265609460, argv=0x8125a58)
    at /mnt/usbstick/KDE4/build/kdesdk/kate/app/kate_dummy.cpp:3
#0  0xb7f86410 in ?? ()
Comment 1 Thomas Friedrichsmeier 2007-12-14 15:19:39 UTC
This might have been kate's fault, or it might have been a problem in kio.

Could you provide some more info:
1) Was this reproducible, or did it only happen once?
2) If it was reproducible, can you still reproduce with a more recent snapshot?
3) If it is still reproducible, could you provide the link that lead to the broken progess dialog / crash?
Comment 2 Benjamin K. Stuhl 2008-01-07 02:27:35 UTC
SVN commit 758150 by bks:

Fix occasional blank KIO progress windows that crash when you interact with them

The problem was that jobs were not unregistered, and so if you happened to get
a job allocated where a previous job had been, the old job was still registered
and confused everything. Fix this by unregistering in the tracker widget's destructor,
but make sure not to delete the widget twice.

CCBUG: 151759


 M  +0 -4      kdecore/jobs/kjobtrackerinterface.cpp  
 M  +1 -1      kdeui/jobs/kwidgetjobtracker.cpp  
 M  +4 -2      kdeui/jobs/kwidgetjobtracker_p.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=758150
Comment 3 Dominik Haumann 2008-12-15 12:24:44 UTC
Hi Martin, can you still reproduce with current trunk?
Comment 4 Christoph Cullmann 2009-04-22 16:07:25 UTC
Assuming is fixed, no feedback since months.