Closed
Bug 776532
Opened 12 years ago
Closed 11 years ago
crash in js::InvokeKernel
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: kairo, Unassigned)
Details
(Keywords: crash, regression, Whiteboard: [js:p1])
Crash Data
This bug was filed from the Socorro interface and is
report bp-0733fd1a-b7b8-42c6-a880-c3fc62120722 .
=============================================================
Stack trace:
0 mozjs.dll js::InvokeKernel js/src/jsinterp.cpp:327
1 mozjs.dll js::Invoke js/src/jsinterp.cpp:388
2 mozjs.dll JS_CallFunctionValue js/src/jsapi.cpp:5572
3 xul.dll nsXPCWrappedJSClass::CallQueryInterfaceOnJSObject js/xpconnect/src/XPCWrappedJSClass.cpp:263
4 xul.dll nsXPCWrappedJS::GetNewOrUsed js/xpconnect/src/XPCWrappedJS.cpp:302
5 xul.dll XPCConvert::JSObject2NativeInterface js/xpconnect/src/XPCConvert.cpp:1119
6 xul.dll XPCConvert::JSData2Native js/xpconnect/src/XPCConvert.cpp:786
7 xul.dll XPCWrappedNative::CallMethod js/xpconnect/src/XPCWrappedNative.cpp:2382
8 xul.dll XPC_WN_CallMethod js/xpconnect/src/XPCWrappedNativeJSOps.cpp:1474
9 mozjs.dll js::InvokeKernel js/src/jsinterp.cpp:345
10 mozjs.dll js::Interpret js/src/jsinterp.cpp:2426
11 mozjs.dll js::InvokeKernel js/src/jsinterp.cpp:356
12 mozjs.dll js::Invoke js/src/jsinterp.h:119
13 mozjs.dll js::CallOrConstructBoundFunction js/src/jsfun.cpp:866
14 mozjs.dll js::InvokeKernel js/src/jsinterp.cpp:345
15 mozjs.dll js::Interpret js/src/jsinterp.cpp:2426
16 nspr4.dll PR_Unlock nsprpub/pr/src/threads/combined/prulock.c:315
17 MMDevAPI.dll _CRT_INIT
18 xul.dll XPCConvert::NativeData2JS js/xpconnect/src/xpcprivate.h:3302
19 @0x21bf
More reports at https://crash-stats.mozilla.com/report/list?signature=js%3A%3AInvokeKernel%28JSContext*%2C%20JS%3A%3ACallArgs%2C%20js%3A%3AMaybeConstruct%29
This apparently has started with the trunk build 2012071503 and affects 16 and 17.
Comment 1•12 years ago
|
||
It first appeared in 16.0a1/20120705.
OS: All → Windows 7
Hardware: All → x86
Updated•12 years ago
|
Whiteboard: [js:p1:fx17]
Comment 2•12 years ago
|
||
Giving a quick look at the stacks, it seems likely that these are really jit crashes: the innermost frame is at an unknown location and the innermost known caller is RunScript.
Comment 3•12 years ago
|
||
It's #25 top browser crasher in 15.0b3, #32 in 16.0a2 and #27 in 17.0a1 while only #273 in 14.0.1.
Crash Signature: [@ js::InvokeKernel(JSContext*, JS::CallArgs, js::MaybeConstruct)] → [@ js::InvokeKernel(JSContext*, JS::CallArgs, js::MaybeConstruct) ]
Keywords: regression
Version: Trunk → 15 Branch
Updated•12 years ago
|
Crash Signature: [@ js::InvokeKernel(JSContext*, JS::CallArgs, js::MaybeConstruct) ] → [@ js::InvokeKernel(JSContext*, JS::CallArgs, js::MaybeConstruct) ]
[@ js::InvokeKernel(JSContext*, js::CallArgs, js::MaybeConstruct) ]
Updated•12 years ago
|
tracking-firefox15:
--- → ?
tracking-firefox16:
--- → ?
tracking-firefox17:
--- → ?
Keywords: topcrash
Comment 4•12 years ago
|
||
This is currently a pretty low volume crash so I'm not tracking it for now. If we get more user feedback in crash reports or a spike of crashes on a particular build that help us find the cause we can re-evaluate based on that.
Comment 5•12 years ago
|
||
(In reply to Lukas Blakk [:lsblakk] from comment #4)
> This is currently a pretty low volume crash
Can you clarify the threshold so that I don't ask a tracking for #14 top crasher (without hangs) in 15.0b3?
Updated•12 years ago
|
Whiteboard: [js:p1:fx17] → [js:p1:fx18][js:bumped:1]
Comment 6•12 years ago
|
||
top 30 crash in Firefox 16.0.1, when one combines the two crash signatures.
And top 5 among js:: crash signatures.
Reporter | ||
Comment 7•12 years ago
|
||
This is the #8 topcrash in trunk over the last 3 days, so nominating for tracking.
tracking-firefox19:
--- → ?
Comment 8•12 years ago
|
||
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #7)
> This is the #8 topcrash in trunk over the last 3 days, so nominating for
> tracking.
99% of crashes happen on 64-bit builds that are not tracked for release.
tracking-firefox19:
? → ---
Hardware: x86 → All
Comment 9•12 years ago
|
||
It's #27 top browser crasher w/o hangs in 17.0 so no longer longer a top crasher (arbitrary restricted to the top 20).
Keywords: topcrash
Updated•12 years ago
|
Whiteboard: [js:p1:fx18][js:bumped:1] → [js:p1]
Comment 10•11 years ago
|
||
We don't have any reports from versions >22. Based on that and comment 2, I'm resolving under the assumption that this was fixed by replacing JM with baseline.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•