GNOME Bugzilla – Bug 309875
galeon 1.3.21 crashed on reload on Fedora Core 4
Last modified: 2005-07-12 02:15:42 UTC
Steps to reproduce: 1. install galeon from tarball or from fedora extras rpm. 2. load a page. 3. reload it using the reload button. (insist if it doesnt crash immediatly:p) Stack trace: Program received signal SIGSEGV, Segmentation fault.
+ Trace 61631
Thread 46912497527392 (LWP 12057)
Other information: Bug seems to be reproducible on i386 and x86_64.
Here's a more descriptive stack-trace (with gtk2/glib2/galeon/mozilla debuginfo packages installed) Program received signal SIGSEGV, Segmentation fault.
+ Trace 61632
Thread 46912497527392 (LWP 15707)
It looks like a crash inside mozilla to me. There's no real galeon code in either backtrace. Note that both backtraces are not showing the same stack. You may want to try again and do a 'thread apply all bt' in gdb to get the backtrace from every thread. But I expect that we'll close it as a mozilla bug...
Created attachment 48876 [details] thread apply all bt Here's the backtrace of all threads. There doesnt seem to be anything interesting in the "other threads"... This is not the same stack trace again, but this is always triggered by the same action (click on reload button...), how can that be ? Could that depend of the number of tabs opened ? is that some kind of buffer overflow ? or more likely a race condition, no ?
Well, it's pretty much the same backtrace as in comment #1. I'm pretty sure that galeon doesn't attach any listeners that could end up getting notified by the imgRequest, so I really fail to see how our code is doing anything. You could try running TestGtkEmbed or epiphany and see what that does but I suspect they don't bother including TestGtkEmbed in the mozilla/firefox packages in fc4. If you get a crash with one of those, then it's pretty clearly a mozilla problem, even if it doesn't happen with the mozilla-browser/firefox
I get an immediate crash when reloading on epiphany on x86_64... err, and actually with mozilla itself too! so that makes it a mozilla bug. according to this thread: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=160330 it's probably this mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=293307
Then our work here is done. Thanks for following up.