Re: [sarge] Konqueror 3.3.2 crashes
On Saturday 12 November 2006 03:26, Nick Boyce wrote:
> Over the last couple of weeks I've experienced a series of Konqueror
> crashes using my vanilla Sarge system while surfing the web. A common
> feature seems to be Slashdot. In every case, I had Slashdot pages open,
> and in 3 cases the crash occurred immediately on opening an article link in
> a new tab.
>
> The crash is not repeatable - usually Konqueror behaves fine if I just
> restart it and go back to Slashdot.
Well ... it's getting worse. Tonight I couldn't view Slashdot at all for
several minutes. Something on the front page was killing Konqueror as soon
as the page started loading. At one point the crash couldn't even produce a
backtrace - the crash handler displayed a message saying a stack corruption
prevented a valid backtrace from being produced.
It's gone away again now.
I've hunted around at bugs.kde.org, and similar crashes abound in Konqueror
3.3.2 - in which KJS seems to be a common feature. e.g. :
http://bugs.kde.org/show_bug.cgi?id=94934
http://bugs.kde.org/show_bug.cgi?id=107400
http://bugs.kde.org/show_bug.cgi?id=102632
http://bugs.kde.org/show_bug.cgi?id=109964
From the comments by the bug handlers it seems nobody is going to want to look
further into my problem - a common response is "upgrade to 3.5.2 and see
whether the problem's still there".
Oh well. Might have to switch to Firefox till Etch gets released :(
PS: some of the bug reports talk about needing backtraces with debug symbols,
or using debug builds ... can anyone tell me how one might do that ?
Cheers
Nick Boyce
Bristol, UK
--
Will no one rid me of this troublesome chair ?
Reply to: