launch mozilla -mail hit new message close compose window hit new message again, crash. here's the stack: #0 0x40705371 in nsWidget::OnButtonPressSignal (this=0x82c5030, aGdkButtonEvent=0x824ae50) at nsWidget.cpp:1901 #1 0x4070a920 in nsWindow::HandleGDKEvent (this=0x82c5030, event=0x824ae50) at nsWindow.cpp:1118 #2 0x406f61bd in handle_gdk_event (event=0x824ae50, data=0x0) at nsGtkEventHandler.cpp:896 #3 0x4087800b in gdk_event_dispatch () from /usr/lib/libgdk-1.2.so.0 #4 0x408a5be6 in g_main_dispatch () from /usr/lib/libglib-1.2.so.0 #5 0x408a61a1 in g_main_iterate () from /usr/lib/libglib-1.2.so.0 #6 0x408a6341 in g_main_run () from /usr/lib/libglib-1.2.so.0 #7 0x407cd209 in gtk_main () from /usr/lib/libgtk-1.2.so.0 #8 0x406eb537 in nsAppShell::Run (this=0x80938d8) at nsAppShell.cpp:304 #9 0x405a1f4d in nsAppShellService::Run (this=0x80abfb8) at nsAppShellService.cpp:455 #10 0x804c1dd in main1 (argc=1, argv=0xbffff934) at nsAppRunner.cpp:597 #11 0x804c667 in main (argc=1, argv=0xbffff934) at nsAppRunner.cpp:690 from gdb: (gdb) print gRollupListener $1 = (nsIRollupListener *) 0x8ad6b04 (gdb) print *gRollupListener $2 = {<nsISupports> = {_vptr. = 0xdadadada}, <No data fields>}

ah, there is a trick to reproducing it. in the first compose window, click on the "from:" picker, and leave it open. while it is open, close the window (I used the window manager to close it) then bring up the compose window again, and crash.

this is a crash and needs to be fixed for beta

Adding "crash" keyword.

Moving over to MailNews product...I think this is fixed already.

This hasn't been fixed. It will go away when Rod Spears fixes 7898.

checked in fix.

Linux (2000-02-16-08 M14) Win32 (2000-02-15-16 M14) Mac (2000-02-16-08 M14) I use the following scenario to re-test the bug. The problem has been fixed. 1. Launch mozilla -mail2. 2. Click on New Message to open the Compose window 3. In the first compose window, click on the "from:" picker, and leave it open. 4. While it is open, close the window (I used the window manager to close it) 5. Bring up the compose window again, and crash.