Closed Bug 441649 Opened 16 years ago Closed 16 years ago

Firefox 3.0 Crash Report [@ nsBaseWidget::RemoveChild(nsIWidget*) ] - metasearch addon


(Toolkit :: Blocklist Policy Requests, defect)

Not set





(Reporter: chofmann, Assigned: fligtar)



(Keywords: topcrash+)


(2 files, 1 obsolete file)

ted spotted this topcrash on firefox 3 after database clean up work

0  	xul.dll  	nsBaseWidget::RemoveChild  	 mozilla/widget/src/xpwidgets/nsBaseWidget.cpp:345
1 	xsupport.dll 	xsupport.dll@0x114d 	
2 	xul.dll 	XPCWrappedNative::CallMethod 	mozilla/js/src/xpconnect/src/xpcwrappednative.cpp:2393
3 	xul.dll 	XPC_WN_CallMethod 	mozilla/js/src/xpconnect/src/xpcwrappednativejsops.cpp:1473
4 	js3250.dll 	js_Invoke 	mozilla/js/src/jsinterp.c:1297
5 	js3250.dll 	js_Interpret 	mozilla/js/src/jsinterp.c:4852
6 	js3250.dll 	js_Invoke 	mozilla/js/src/jsinterp.c:1313
7 	xul.dll 	nsXPCWrappedJSClass::CallMethod 	mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp:1523
8 	xul.dll 	nsXPCWrappedJS::CallMethod 	mozilla/js/src/xpconnect/src/xpcwrappedjs.cpp:559
9 	xul.dll 	PrepareAndDispatch 	mozilla/xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp:114
10 	xul.dll 	SharedStub 	mozilla/xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp:141
11 	xul.dll 	nsEventListenerManager::HandleEventSubType 	mozilla/content/events/src/nsEventListenerManager.cpp:1080

all of he reports seem to showing binary components from this extension

and users don't have a clue about what is causing their startup crash..  comements:

> will not start up don't know what the problem is.

> Unable to access web via Mizilla Firefox 3.0 due to crashes. Can ony access web by using "safe mode."

> STOP THIS MADNESS! I USED TO LOVE FIREFOX BUT NOT ANYMORE! This stupid screen has poped up for 3 days! Do not make me go back to Internet Explorer!

a quick scan of several reports shows that all crashes may be associated with


here is what prevx has to say about the .dll that appears related to the crash

What we know about XSHARED.DLL:
The filename XSHARED.DLL was first seen on May 28 2008 in SPAIN. It has also been seen in the following geographical regions of the Prevx community:

    * The UNITED STATES on Jun 2 2008
    * The EUROPEAN UNION on Jun 2 2008

The filename XSHARED.DLL is used by multiple object types including Dynamic Link LIbraries,objects.
The most common file size is 343,552 bytes. But the following file sizes have also been seen:

    * 361,984 bytes
    * 1,167,964,050 bytes

These files may have the following Vendor, Product, Version Information in the file header; Crawler Firefox Shared Library;

    * The following Vendor, Product, Version Information has also been reported:; Crawler Firefox Shared Library;
XSHARED.DLL has been seen to perform the following behavior(s):

    * The Process is polymorphic and can change its structure

XSHARED.DLL has been the subject of the following behavior(s):

    * Created as a process on disk
    * Deleted as a process from disk
    * Registered as a Dynamic Link Library File

XSHARED.DLL can also use the following file names:

    * A0046354.DLL
    * A0177030.DLL
    * A0005619.DLL
Component: Widget → Extension Compatibility
Keywords: topcrash
Product: Core → Firefox
QA Contact: general → extension.compatibility
looks like a candidate for blocking/sumo doc
I left a ticket at in hopes of getting a contact or response.

Question: xshared.dll in crawler addon not compatible with Firefox 3.0
6/24/2008 1:34:51 PM
Name: Chris Hofmann
Email: <>

Subject: xshared.dll in crawler addon not compatible with Firefox 3.0
Question Description:

There are more details in our bug report please
provide comment there on possible diagnosis or a fix, or
contact me as soon as possible.

Really interesting. Are all those comments coming from the crash report data? ("STOP THIS MADNESS!" etc)

So the solution is to start Firefox in safe mode and uninstall the extension?
yes, that is the theory to be tested..
I did see one comment in a crash report indicating that the user knew it was from this extension, but most of them are the usual "why is my firefox crashing?"

This continues to be our #1 crash on Windows.
Component: Extension Compatibility → Blocklisting
Keywords: topcrashtopcrash+
Product: Firefox →
QA Contact: extension.compatibility → blocklisting
Version: Trunk → unspecified
SQL to blocklist verison 1.2 in Firefox 3:

INSERT INTO blitems (guid, min, max, created, modified) VALUES('{4B3803EA-5230-4DC3-A7FC-33638F3D3542}', '1.2', '1.2', NOW(), NOW());

INSERT INTO blapps (blitem_id, guid, min, max, created, modified) VALUES((SELECT id FROM blitems WHERE guid='{4B3803EA-5230-4DC3-A7FC-33638F3D3542}'), '{ec8030f7-c20a-464f-9b0e-13a3a9e97384}', '3.0a1', '*', NOW(), NOW());

Installed the add-on in Windows and reproduced Firefox crashing on startup every time. Crashing did not occur after the add-on was blocklisted. I only blocked version 1.2 because I didn't see any other version numbers around on the site. 
Assignee: nobody → fligtar
OS: Mac OS X → All
Hardware: PC → All
Attachment #326637 - Flags: review?(morgamic)
Attachment #326639 - Flags: review?(morgamic)
Depends on: 423968
actually this looks like the #1 and #2 topcrash, somehow some of the crash reports don't have symbols, but looking at them they have the same stack.
I filed bug 442234 about some of those reports not having symbols.
morgamic, can we get this reviewed so we can blocklist this add-on?
Attachment #326637 - Flags: review?(morgamic) → review+
Comment on attachment 326639 [details] [diff] [review] blocklist patch

I can add this to the blocklist info page after the SQL is run.
Attachment #326639 - Flags: review?(morgamic) → review+
Depends on: 444124
Filed bug 444124 to run the blocklist SQL.
Checked in update in r16798. morgamic, can you push live? update was pushed live.
Closed: 16 years ago
Resolution: --- → FIXED
looks like it did the trick...  no longer in the top 100 looking at latest 3.0.1 top crashes.
The content of attachment 375533 [details] has been deleted by
    Dave Miller [:justdave] <>
who provided the following reason:

Windows EXE file, unrelated to bug

The token used to delete this attachment was generated at 2009-05-03 14:40:24 PDT.
Product: → Toolkit
You need to log in before you can comment on or make changes to this bug.