RE: Linux seamonkey build (1999-04-12-09) Steps 1. Run apprunner.exe 2. From Tasks, select Messenger, 3. I get a core dump from launching mail application. Unable to do further mail testings. This problem occurs to other QA too. FindMsgAppCore: Creating AppCore Initializing MsgAppCore and setting Window nsMsgAppCore::SetWindow(): Getting the webShell of interest... Segmentation fault (core dumped)

This is not happening when launching mail for me, but when getting messages. Makes the build pretty useless.

New regression for the 4-12 build on Linux. Setting target milestone to M4 since this is a stopper for us.

Geez. Seth tells me that he's crashing on the M5 tree and not the M4 branch. QA has been just getting one notification from release team and there is no mention whether the builds they're telling us about are M4 branch or M5. Jan will clarify; meanwhile, Seth will look into the crash.

here's a stack trace: #0 0x40e3e3ed in ?? () #1 0x40e45cf9 in ?? () #2 0x40e45c0d in ?? () #3 0x40d699b0 in ?? () #4 0x40d6a70c in ?? () #5 0x4069a472 in js_Invoke (cx=0x82f5578, argc=0, constructing=0) at jsinterp.c:650 #6 0x406a07d6 in js_Interpret (cx=0x82f5578, result=0xbfffebdc) at jsinterp.c:2183 #7 0x4069a4c0 in js_Invoke (cx=0x82f5578, argc=0, constructing=0) at jsinterp.c:666 #8 0x406a07d6 in js_Interpret (cx=0x82f5578, result=0xbfffedf4) at jsinterp.c:2183 #9 0x4069a4c0 in js_Invoke (cx=0x82f5578, argc=0, constructing=0) at jsinterp.c:666 #10 0x406a07d6 in js_Interpret (cx=0x82f5578, result=0xbffff00c) at jsinterp.c:2183 #11 0x4069a4c0 in js_Invoke (cx=0x82f5578, argc=1, constructing=0) at jsinterp.c:666 #12 0x4069a6a1 in js_CallFunctionValue (cx=0x82f5578, obj=0x83f2e70, fval=138358392, argc=1, argv=0xbffff130, rval=0xbffff134) at jsinterp.c:735 #13 0x406837f9 in JS_CallFunctionValue (cx=0x82f5578, obj=0x83f2e70, fval=138358392, argc=1, argv=0xbffff130, rval=0xbffff134) at jsapi.c:2369 #14 0x406272a7 in nsJSEventListener::HandleEvent (this=0x84633c0, aEvent=0x8432a00) at nsJSEventListener.cpp:93 #15 0x403de671 in nsEventListenerManager::HandleEvent (this=0x8462ba0, aPresContext=@0x83d8e80, aEvent=0xbffff248, aDOMEvent=0xbffff20c, aFlags=3, aEventStatus=@0xbffff3f4) at nsEventListenerManager.cpp:555 #16 0x40c2a2d9 in ?? () #17 0x403dfafc in nsEventStateManager::CheckForAndDispatchClick (this=0x8470598, aPresContext=@0x83d8e80, aEvent=0xbffff480, aStatus=@0xbffff3f4) at nsEventStateManager.cpp:398 #18 0x403df529 in nsEventStateManager::PostHandleEvent (this=0x8470598, aPresContext=@0x83d8e80, aEvent=0xbffff480, aTargetFrame=0x8465540, aStatus=@0xbffff3f4) at nsEventStateManager.cpp:149 #19 0x40407989 in PresShell::HandleEvent (this=0x8403e58, aView=0x83ff950, aEvent=0xbffff480, aEventStatus=@0xbffff3f4) at nsPresShell.cpp:2106 #20 0x40df51fa in ?? () #21 0x40dfcce9 in ?? () #22 0x40df3c0e in ?? () #23 0x4008556e in nsWidget::DispatchEvent (this=0x83ff9b8, event=0xbffff480, aStatus=@0xbffff430) at nsWidget.cpp:909 #24 0x400854c5 in nsWidget::DispatchWindowEvent (this=0x83ff9b8, event=0xbffff480) at nsWidget.cpp:871 #25 0x400855eb in nsWidget::DispatchMouseEvent (this=0x83ff9b8, aEvent=@0xbffff480) at nsWidget.cpp:936 #26 0x40082f94 in handle_button_release_event (w=0x83ffa80, event=0x81e7258, p=0x83ff9b8) at nsGtkEventHandler.cpp:541 #27 0x408a0c49 in gtk_marshal_BOOL__POINTER () #28 0x40862915 in gtk_handlers_run () #29 0x40861c8e in gtk_signal_real_emit () #30 0x4085fc5f in gtk_signal_emit () #31 0x40897928 in gtk_widget_event () #32 0x408335e2 in gtk_propagate_event () #33 0x40832768 in gtk_main_do_event () #34 0x408dcc8b in gdk_event_dispatch () #35 0x4090add2 in g_main_dispatch () #36 0x4090b3bb in g_main_iterate () #37 0x4090b571 in g_main_run () #38 0x4083215b in gtk_main () #39 0x4007d145 in nsAppShell::Run (this=0x8144600) at nsAppShell.cpp:208 #40 0x40013f5a in nsAppShellService::Run (this=0x8126018) at nsAppShellService.cpp:186 #41 0x804a631 in main (argc=1, argv=0xbffffa14) at nsAppRunner.cpp:506

This should be moved to M5. This bug does not occur on second April 09 build, correct? This is a April 12 build bug yes? If so, please move to M5.

Yes, this is an M5 bug. 1999040915 (M4 builds) are ok.

I just checked in the fix. It was causing a crash on Linux and Windows. (curse uninitialized memory.)

I just checked in the fix. It was causing a crash on Linux and Windows. (curse uninitialized memory.)

RE: Linux builds (1999-04-16-08, 1999-04-19-08,1999-04-20-08 and 1999-04-21-08) RE: win32 builds (1999-04-16-08, 1999-04-19-08,1999-04-20-10 and 1999-04-21-08) I verify that mail application no longer crashes in these builds.