in M7 In the sidbar customisation window clicking on customise in the top half a second time causes a GPF: ---------------------------------------------- APPRUNNER caused an invalid page fault in module JS3250.DLL at 0177:004f8c7e. Registers: EAX=00891b80 CS=0177 EIP=004f8c7e EFLGS=00010202 EBX=02a779b0 SS=017f ESP=0076f428 EBP=0076f42c ECX=0238d4e0 DS=017f ESI=00000000 FS=6d77 EDX=1001e894 ES=017f EDI=025feaa8 GS=0000 Bytes at CS:EIP: 8b 4e 24 8d 46 24 83 e1 fe 3b 4d 10 75 05 ff 46 Stack dump: 00000000 0076f44c 004f8d9d 02a779b0 00000000 00891b80 02a779b0 02c3b830 025feaa8 0076f498 004fcb47 00891b80 025feaa8 02a779b0 007fe464 00000000 ----------------------------------------------

Happens on latest 6/23 builds, Mac also. To reproduce, simply bring up the Customize Screen, then click twice on Customize button. Thanks for the bug report! Sending to matt, as I believe it is his area.

*** Bug 8802 has been marked as a duplicate of this bug. ***

*** Bug 8787 has been marked as a duplicate of this bug. ***

Here's the stack trace - the link to the talkback report is in the URL field above. Call Stack: (Signature = js_LockScope1 626cb4fb) js_LockScope1 [d:\builds\seamonkey\mozilla\js\src\jslock.c, line 629] js_LockObj [d:\builds\seamonkey\mozilla\js\src\jslock.c, line 703] js_SetProperty [d:\builds\seamonkey\mozilla\js\src\jsobj.c, line 1924] js_Interpret [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 2195] js_Invoke [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 675] js_InternalCall [d:\builds\seamonkey\mozilla\js\src\jsinterp.c, line 749] JS_CallFunctionValue [d:\builds\seamonkey\mozilla\js\src\jsapi.c, line 2633] nsJSEventListener::HandleEvent [d:\builds\seamonkey\mozilla\dom\src\events\nsJSEventListener.cpp, line 98] nsEventListenerManager::HandleEvent [d:\builds\seamonkey\mozilla\layout\events\src\nsEventListenerManager.cpp, line 572] nsGenericElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\layout\base\src\nsGenericElement.cpp, line 784] nsHTMLButtonElement::HandleDOMEvent [d:\builds\seamonkey\mozilla\layout\html\content\src\nsHTMLButtonElement.cpp, line 375] nsEventStateManager::CheckForAndDispatchClick [d:\builds\seamonkey\mozilla\layout\events\src\nsEventStateManager.cpp, line 633] nsEventStateManager::PostHandleEvent [d:\builds\seamonkey\mozilla\layout\events\src\nsEventStateManager.cpp, line 195] PresShell::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 2051] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 833] nsViewManager::DispatchEvent [d:\builds\seamonkey\mozilla\view\src\nsViewManager.cpp, line 1735] HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 67] nsWindow::DispatchEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 423] nsWindow::DispatchWindowEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 440] nsWindow::DispatchMouseEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3066] ChildWindow::DispatchMouseEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3213] nsWindow::ProcessMessage [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2370] nsWindow::WindowProc [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 483] KERNEL32.DLL + 0x3663 (0xbff73663) KERNEL32.DLL + 0x22894 (0xbff92894) 0x00758c20

Hmm, I'm seeing a pile of asserts in the table code when I click on "customize..." now; so many I can't really even bring up the dialog. slamm, you know 'bout this?

Yeah, this has to do with the table headers. Hyatt has a separate bug on that. Marking it as a dependency.

I've stopped the assertion, but we are still having some problems with the sidebar-registry.rdf getting clobbered. The second time you bring up the window, it "refreshes" the RDF/XML from disk, but the available panels list is empty. I've noticed that we're affected by the dreaded event listener leak (8159), so I'm gonna try to fix that first. Marking as dependent.

Changed RDF service to a global. This fixed it. I have no idea why.

marking this bug verified, I filed another one to slamm about the panels being empty the second time, which still appears in 8/9 builds