Closing Bug 69906

[Megan Webb]

I've been looking through the bugs, and testing/commenting/closing
bugs if I can. 

This bug is the most hated.

It's become a 'catch all' for any crash on kdevelop open, or project open
that has ever happened.

Some of the crashes are because of other bugs - that are fixed, or have
not been looked at yet. Its hard to tell now. The bug was started back in
2003, with kdevelop 3.0.0.

Because of the long history, and varied crashes listed here, it's hard to
trace through it and get anything useful.

The last comment does look useful, and happily has a patch:

/------- Additional Comment #102
<http://bugs.kde.org/show_bug.cgi?id=69906#c102> From Carsten Pfeiffer
<mailto:pfeiffer at kde.org> 2006-09-28 12:36 ------- /
Created an attachment (id=17953)
<http://bugs.kde.org/attachment.cgi?id=17953&action=view>
patch fixing a crash on shutdown

kdevelop uses a few singleton objects that are never deleted on exit,
and which
are the "owners" of quite a bunch of other objects. When closing the main
window with Alt-F4 for example, the QObject hierarchy will make sure that
(almost) everything is deleted in the right order.

When closing kdevelop through session management, or e.g. via "dcop `dcop
kdevelop*` MainApplication-Interface quit" however, kdevelop is being
closed
with the last window (and hence all its child objects) still alive.

Can anyone with more knowledge comment on this?  ( Carsten has a kde.org
email address btw.)

I can confirm that it does work for me. 

(The dcop close does cause a crash, and for me corrupted a plugin config
file,
causing a crash on open every time after that.)

Can anyone offer any reason why not to:
- apply this patch
- close this bug with an appropriate comment.


If I do not get any clear indication on what to do, in the next 4 days,
I'll apply
the patch and close the bug.


thanks


Megan