Closed Bug 1011075 Opened 10 years ago Closed 8 years ago

crash in FinalizeTypedArenas<JSObject> first appeared on 2014-05-14

Categories

(Core :: JavaScript: GC, defect)

31 Branch
x86
Windows NT
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox30 --- unaffected
firefox31 + wontfix

People

(Reporter: u279076, Unassigned)

References

Details

(Keywords: crash, topcrash-win)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-bfb086cf-d064-490c-a92b-e1c052140514.
=============================================================
0 	mozjs.dll 	FinalizeTypedArenas<JSObject> 	js/src/jsgc.cpp
1 	mozjs.dll 	FinalizeArenas 	js/src/jsgc.cpp
2 	nss3.dll 	_PR_MD_WAIT_CV 	nsprpub/pr/src/md/windows/w95cv.c

=============================================================
More reports:
https://crash-stats.mozilla.com/report/list?signature=FinalizeTypedArenas%3CJSObject%3E#tab-reports

This is a new signature which first appeared with yesterday's builds. So far I'm only seeing reports with that build (ie. No other Firefox versions seem to be affected).

https://hg.mozilla.org/releases/mozilla-aurora/pushloghtml?fromchange=799d1ce4d82e&tochange=fcbb78e6392e
There's nothing obvious in the regression range, but it's a small enough range that maybe one of the authors there can spot the issue?
This has been rising significantly and is now the #2 topcrash for Firefox 31.
Keywords: crashtopcrash-win
FYI, I've sent an email to all the engineers indicated in the pushlog from comment 0. Hopefully that yeilds some successful results.
It's the AMD bug again :(

Cpu info facet Rank 	Cpu info 	Count 	%
1 	AuthenticAMD family 20 model 1 stepping 0 | 2 	60 	49.18 %
2 	AuthenticAMD family 20 model 2 stepping 0 | 2 	50 	40.98 %
3 	AuthenticAMD family 20 model 1 stepping 0 | 1 	12 	9.84 %
Depends on: 772330
Keywords: crash
Indeed. Don't need to track further.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
OK, untracking.
Looks like it's back again with 31b2:
https://crash-analysis.mozilla.com/rkaiser/2014-06-22/2014-06-22.firefox.31.explosiveness.html

I think we should keep this tracked until after we release, just to be safe.
Anthony, I am then reopening this bug.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
I can't get into supersearch at the moment, but from a quick glance the 31b crashes are not AMD-related. It is likely a real code issue this time.
Does the timing of this match up with GGC? The crash addresses are all over the place. There's a bit of variation in stacks but they usually share:

FinalizeTypedArenas<JSObject>
FinalizeArenas
SweepBackgroundThings
Hmm, I don't see this signature too much with anything other than 31.0b2 or 31.ob3, the newer betas seem to not suffer from it.
Kairo, do you think we can mark this bug as fixed for 31 (at least)?
Flags: needinfo?(kairo)
(In reply to Sylvestre Ledru [:sylvestre] from comment #13)
> Kairo, do you think we can mark this bug as fixed for 31 (at least)?

No, fixed would imply that we actually applied a fix and I don't know of any. wontfix might be fine,t hough, given those are low volume now.
Flags: needinfo?(kairo)
OK. Wontfix then. Thanks!
Crash Signature: [@ FinalizeTypedArenas<JSObject>] → [@ FinalizeTypedArenas<JSObject>] [@ FinalizeTypedArenas<T>]
Bug 1232229 seems to be a newer bug for this signature.
Status: REOPENED → RESOLVED
Closed: 10 years ago8 years ago
Component: JavaScript Engine → JavaScript: GC
Resolution: --- → WORKSFORME
See Also: → 1232229
You need to log in before you can comment on or make changes to this bug.