981681 - startup crash in XREMain::XRE_main(int, char** const, nsXREAppData const*)

Status: RESOLVED MOVED

(Core :: General, defect)

Description

[u279076]

This bug was filed from the Socorro interface and is 
report bp-9de472e7-cc13-4ccc-ae5d-3308a2140310.
=============================================================
0 		@0xf26080 	
1 	xul.dll 	XREMain::XRE_main(int,char * * const,nsXREAppData const *) 	toolkit/xre/nsAppRunner.cpp
2 	xul.dll 	XRE_main 	toolkit/xre/nsAppRunner.cpp
3 	firefox.exe 	do_main 	browser/app/nsBrowserApp.cpp
4 	firefox.exe 	NS_internal_main(int,char * *) 	browser/app/nsBrowserApp.cpp
5 	firefox.exe 	wmain 	toolkit/xre/nsWindowsWMain.cpp
6 	firefox.exe 	__tmainCRTStartup 	f:/dd/vctools/crt_bld/self_x86/crt/src/crtexe.c
7 	kernel32.dll 	BaseProcessStart

More reports: https://crash-stats.mozilla.com/report/list?product=Firefox&signature=XREMain%3A%3AXRE_main%28int%2C+char%2A%2A+const%2C+nsXREAppData+const%2A%29

Module Correlations:
71% (224/316) vs.  23% (23583/101657) ws2help.dll
71% (224/316) vs.  23% (23591/101657) iphlpapi.dll
49% (156/316) vs.   6% (6394/101657) msctfime.ime
99% (314/316) vs.  72% (73127/101657) firefox.exe
100% (316/316) vs.  73% (73851/101657) dbghelp.dll
27% (85/316) vs.  15% (15695/101657) MSCTF.dll
13% (41/316) vs.   4% (4290/101657) msvcp80.dll
77% (242/316) vs.  70% (71050/101657) secur32.dll
8% (26/316) vs.   2% (1583/101657) atl80.dll
20% (62/316) vs.  13% (13191/101657) MSCTFIME.IME
7% (22/316) vs.   1% (1405/101657) OptProCrash.dll
7% (22/316) vs.   1% (1451/101657) lmrn.dll

Add-on Correlations:
NULL

URL Correlations:
1 	http://www.phimsexdvd.com/red-hot-jam-vol-287-real-h-story-ruru-kinouchi-2/

Platforms:
Windows XP 	79.33 %	3784
Windows 7 	17.15 %	818
Windows Vista 	3.40 %	162 

Product:
Firefox 	27.0.1 	82.14 %	3918
Firefox 	26.0 	4.30 %	205
Firefox 	28.0b8 	3.67 %	175
Firefox 	28.0b9 	1.74 %	83
Firefox 	28.0b7 	0.92 %	44 

=============================================================

This crash is not necessarily new but it has appeared as a new spike in Firefox 28 and currently ranks at #68. It currently has a 3-day explosiveness rating of 5.0:
https://crash-analysis.mozilla.com/rkaiser/2014-03-09/2014-03-09.firefox.28.explosiveness.html

Comment 1

[Benjamin Smedberg]

ni?dmajor for a better stack; we're missing at least one frame and maybe two.

Comment 2

[(Away)]

xul!ScopedXPCOMStartup::Initialize
xul!XREMain::XRE_main
xul!XRE_main
firefox!do_main
firefox!NS_internal_main
firefox!wmain

This is strange. Stack remnants indicate that we were inside xul!ScopedXPCOMStartup::Initialize trying to call xul!NS_InitXPCOM2, but that call didn't land at its destination.

NS_InitXPCOM2 is an exported symbol, so it's possible that somebody could have obtained the address and hooked it -- but I don't see anything suspicious on the correlations list.

Comment 3

[(Away)]

Oddly enough this is not crashing on recent builds. No hits on 30 and 31. Only a small handful on 29, and they stop after the March 27th build.

Comment 4

[Sylvestre Ledru [:Sylvestre]]

OK. A side effect of an other patch?

Updating the tracking flags then...

Comment 5

[Ioana (away)]

There are two crashes on the 03/31 Firefox 29, but no crashes on newer builds of any version:
https://crash-stats.mozilla.com/report/list?product=Firefox&signature=XREMain%3A%3AXRE_main%28int%2C+char%2A%2A+const%2C+nsXREAppData+const%2A%29#tab-reports

Comment 6

[BugBot [:suhaib / :marco/ :calixte]]

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Comment 7

[BugBot [:suhaib / :marco/ :calixte]]

The bug is linked to a topcrash signature, which matches the following criterion:

• Top 20 desktop browser crashes on beta (startup)

:bhood, could you consider increasing the severity of this top-crash bug?

For more information, please visit BugBot documentation.

Comment 8

[Jens Stutte [:jstutte]]

We moved the monitoring of this signature to bug 1909700, as of today it is only happening for NS_ERROR_OMNIJAR_CORRUPT/_MISSING.