2000091408 this has happened to me 4 times today: when i have added comment in bugzilla, hit submit and then close the resulting window while it is still loading, moz crashes very often. bt from non-debug: Program received signal SIGSEGV, Segmentation fault. 0x40333f0e in main_arena () from /lib/libc.so.6 (gdb) bt #0 0x40333f0e in main_arena () from /lib/libc.so.6 #1 0x4070aa59 in NSGetModule () from /tmp/package/components/libwidget_gtk.so #2 0x4089d149 in g_idle_dispatch () from /usr/lib/libglib-1.2.so.0 #3 0x4089c186 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0 #4 0x4089c751 in g_main_iterate () from /usr/lib/libglib-1.2.so.0 #5 0x4089c8f1 in g_main_run () from /usr/lib/libglib-1.2.so.0 #6 0x407c47b9 in gtk_main () from /usr/lib/libgtk-1.2.so.0 #7 0x406fa73c in NSGetModule () from /tmp/package/components/libwidget_gtk.so #8 0x4045d38a in inflate_mask () from /tmp/package/components/libnsappshell.so #9 0x804db37 in JS_PushArguments () #10 0x804df96 in JS_PushArguments () #11 0x4025d9cb in __libc_start_main (main=0x804de8c <JS_PushArguments+11368>, argc=1, argv=0xbffff894, init=0x804ada4 <_init>, fini=0x805361c <_fini>, rtld_fini=0x4000ae60 <_dl_fini>, stack_end=0xbffff88c) at ../sysdeps/generic/libc-start.c:92 (gdb) quit

keyw.

trying to reproduce this at http://landfill.tequilarista.org/bugzilla/ will report back. R.K.Aa are you using a talkback build (the /mozilla-i686-pc-linux-gnu-sea.tar.gz builds allow you to pick Talkback as an installed component) If so is it generating a talkback report?

I'm guessing that the resulting page is loading very slow because of Bugzilla's problems today and the reason I can't repor it at the test bugzilla installation is that it is running too fast. I'll try some on a test bug at bugzilla.

R.K.Aa was this the only mozilla window you had open or did you have a remaining window after closing the bug result window? I couldn't repro it on bugzilla.mozilla.org either. Will try again later.

had two windows open at the time. One was passive, was using the other, and when closing that other while it was loading - crash. Not using talkback builds (shame on me).

can you reproduce this or was this a one-timer?

This looks very simillar to bug 53704.

i crash all the time when closing a loading window now (when throbber still throbs). Haven't seen this exact trace again; the current crashes look different and the one i filed about that was made dup of bug 53613

can you get a talkback on this?

currently using SEA tarballs, and talkback doesn't work in those. Will try installer via net next time.

R.K.Aa, have you been able to reproduce this problem in the last few weeks?

SEA linux 2000102321 TRUNK! :) Tested it with cnn.com right now and crashed on first attempt, but not running gdb at the time. Tried 5 more times WITH gdb and couldn't repeat the crash. Mozilla does seem to have gotten more robust now. It was *much* easyer to "provoke" this crash some weeks ago, i didn't even really have to try.

Kristin, seeing this still. I've tried and tried to get a crash with a talkback build and cant.

R.K.Aa, any chance you can test this again. If you are still crashing can you get one of the Installer builds (the sea.tar.gz's talkback is broken) and see if it generates a report.

Havent seen it for a while. WFM.

Would you believe it.. it happened again, when closing a second bugwindow loading after adding a comment. Wasn't running via gdb, but the problem is still there - somewhere. Reopening.

that was with a build from 20001212

I don't know if it's related but I crashed a lot lately after submitting changes to a bug then closing the window. Except that this was on _Windows_. The build I'm using is 2000-12-23-08 on WinME. It exits with MSVC library complaining about a "Pure virtual function call".

I'm so far unable to recreate this in 2000-12-26-04 build.

R.K.Aa, still seeing this? Installer builds or the talkback.tar.gz of 0.8 might give us some talkback on this.

Not seen for a while. Perhaps it was a variant of that "crash when closing window while image loading" bug. Which is fixed now. (forgot #). WFM yet again.