525517 - crash [@ XPCCallContext::XPCCallContext(XPCContext::LangType, JSContext*, JSObject*, JSObject*, int, unsigned int, int*, int*)]

Status: RESOLVED INCOMPLETE

(MailNews Core :: Backend, defect)

Description

[Wayne Mery (:wsmwk)]

crash [@ XPCCallContext::XPCCallContext(XPCContext::LangType, JSContext*, JSObject*, JSObject*, int, unsigned int, int*, int*)]

#1 crash for 2.0, from crash-stats
all versions of windows, no Mac
and only 2.0, no betas - so many extensions/install/uninstall related?

3 comments
- I tried to uninstall sea monkey 1.1.18 but sea monkey 2.0 was still runnng
- I get an error message when trying to play games or certain site thats says add-ons disable even in internet explorer can you please me thanks yahoo.com games spades

- Started Uninstall of old SeaMonkey 1.1.16
bp-70d928ac-4147-4da5-b8f9-7fc8b2091017
0	seamonkey.exe	XPCCallContext::XPCCallContext	 js/src/xpconnect/src/xpccallcontext.cpp:127
1	seamonkey.exe	GetContextFromObject	js/src/xpconnect/src/xpcwrappedjsclass.cpp:585
2	seamonkey.exe	nsXPCWrappedJSClass::CallMethod	js/src/xpconnect/src/xpcwrappedjsclass.cpp:1628
3	seamonkey.exe	nsXPCWrappedJS::CallMethod	js/src/xpconnect/src/xpcwrappedjs.cpp:569
4	xpcom_core.dll	PrepareAndDispatch	xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp:114
5	xpcom_core.dll	SharedStub	xpcom/reflect/xptcall/src/md/win32/xptcstubs.cpp:141

Comment 1

[Robert Kaiser]

I wonder if this is connected with bug 526202

Comment 2

[Robert Kaiser]

Forwarding blocking request to next security/stability update. If this crash is happening frequently, we really would like to get a hold on it...

Neil, any chance to find out what really goes wrong there?

Comment 3

[[e-mail]]

That stack makes no sense, unless perhaps it was called from JS, which is a problem since the fix to make JS stacks unwind correctly only landed recently.

Comment 4

[Robert Kaiser]

http://crash-stats.mozilla.com/topcrasher/byversion/SeaMonkey/2.0 still has this high-ranking on its list, http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&signature=XPCCallContext%3A%3AXPCCallContext%28XPCContext%3A%3ALangType%2C%20JSContext%2A%2C%20JSObject%2A%2C%20JSObject%2A%2C%20int%2C%20unsigned%20int%2C%20int%2A%2C%20int%2A%29&version=SeaMonkey%3A2.0 shows more reports (147 last week).

Interestingly, Firefox has the same signature on the list, with 1021 reports last week, at rank #247 on their 3.5.5 topcrash list right now.

Comment 5

[Serge Gautherie (:sgautherie)]

(In reply to comment #4)
> Interestingly, Firefox has the same signature on the list

Should this bug be moved to Core then?
Or is there a Firefox bug already filed to depend on?

Comment 6

[Robert Kaiser]

(In reply to comment #5)
> Should this bug be moved to Core then?
> Or is there a Firefox bug already filed to depend on?

If you can figure out from the stack that this is really a cross-application
crash and not just something that does something wrong in our code and that
bubbles up to crash at a place where other things also cause a crash, then
sure.

Else it would be good to investigate this.

Comment 7

[Robert Kaiser]

I can't find this crash on the Firefox topcrash lists right now, but it's still #6 for SeaMonkey 2.0.2 - and #24 for Thunderbird 3.0.1, Windows-only for both.

The top few frames in the stacks are pretty uniform across the reports, but those all look like core code and without any good C++ code knowledge, I can't really make out anything there, I can't spot any SeaMonkey- or Thunderbird-specific code in most of the stacks, but I'll defer judgment to people who know more.

As it appears on topcrash lists for both Thunderbird 3.0.1 and SeaMonkey 2.0.2 but nor Firefox 3.5.7 or 3.6, I'll move it to MailNews Core for now.

Comment 8

[Wayne Mery (:wsmwk)]

has morphed to XPCCallContext::XPCCallContext(XPCContext::LangType, JSContext*, JSObject*, JSObject*, int, unsigned int, unsigned __int64*, unsigned __int64*) 

did not compare TB stacks [1] to FF stacks [2], but note the firefox crash rate is much lower than TB, and FF crashes are almost all startup whereas TB is mostly not

[1] https://crash-stats.mozilla.com/report/list?product=Thunderbird&query_search=signature&query_type=contains&query=XPCCallContext%3A%3AXPCCallContext%28XPCContext%3A%3ALangType&reason_type=contains&date=10%2F06%2F2011%2002%3A53%3A01&range_value=4&range_unit=weeks&hang_type=any&process_type=any&do_query=1&admin=1&signature=XPCCallContext%3A%3AXPCCallContext%28XPCContext%3A%3ALangType%2C%20JSContext*%2C%20JSObject*%2C%20JSObject*%2C%20int%2C%20unsigned%20int%2C%20unsigned%20__int64*%2C%20unsigned%20__int64*%29

[2] https://crash-stats.mozilla.com/report/list?product=Firefox&query_search=signature&query_type=exact&query=XPCCallContext%3A%3AXPCCallContext%28XPCContext%3A%3ALangType%2C%20JSContext*%2C%20JSObject*%2C%20JSObject*%2C%20int%2C%20unsigned%20int%2C%20unsigned%20__int64*%2C%20unsigned%20__int64*%29&reason_type=contains&date=10%2F06%2F2011%2002%3A55%3A15&range_value=4&range_unit=weeks&hang_type=any&process_type=all&do_query=1&admin=1&signature=XPCCallContext%3A%3AXPCCallContext%28XPCContext%3A%3ALangType%2C%20JSContext*%2C%20JSObject*%2C%20JSObject*%2C%20int%2C%20unsigned%20int%2C%20unsigned%20__int64*%2C%20unsigned%20__int64*%29

Comment 9

[Scoobidiver (away)]

The topcrash- keyword is not actively maintained and pollutes queries with topcrash.

Comment 10

[Wayne Mery (:wsmwk)]

10 tb52 crashes in last 6 months, but none for TB60.
This never had anything remotely identifiable in the crash, so => incomplete