[Bug 357016] Re: kile crashed with SIGSEGV in QWidgetPrivate::deleteExtra()

[thecalbear at gmail.com]

I was experiencing the Signal 11 crash from the default Kile in Jaunty
as well, and I downloaded the experimental Kile provided by Andreas
Wenning here. It seemed to have improved on the frequency of crash: now
it crashes *only after* I quit Kile. I've used it for a while now, and I
haven't experienced crashes when I'm working on Kile, so that's a great
thing. Now the crash is only a "nuisance."

But here is an interesting thing:
After I quit Kile, "pgrep kile" still yields a Process ID, until the Signal 11 crash message appears. 
If I re-open Kile before the Signal 11 message appears, the Signal 11 message will appear and Kile will fail to open this one time. Then, "pgrep kile" will yield nothing, and opening Kile again will be fine. 
If I do not try to re-open Kile after quitting Kile (but apparently not completely since pgrep kile still yields the same Process ID), the Signal 11 message will appear at a random time later.

-- 
kile crashed with SIGSEGV in QWidgetPrivate::deleteExtra()
https://bugs.launchpad.net/bugs/357016
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kile in ubuntu.