Closed Bug 1332933 Opened 7 years ago Closed 7 years ago

Crash in js::jit::DoTypeUpdateFallback

Categories

(Core :: JavaScript Engine: JIT, defect, P1)

Unspecified
Android
defect

Tracking

()

RESOLVED FIXED
mozilla53
Tracking Status
firefox-esr45 --- unaffected
firefox52 --- unaffected
firefox53 - fixed

People

(Reporter: marcia, Unassigned)

References

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-8cddb788-d377-45a3-aa50-ba7852170122.
=============================================================

Seen while looking at trunk crashes, started with 20170119222831 build: http://bit.ly/2kh3hgR.


one comment: "I just opened a private tab and put the phone in landscape."

Possible regression range: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=a5253dce8b67c2248d7b92ef664a6dd6664e7609&tochange=a3978751f45108ff1ae002ecebdc0fa23fc52b84
Regression from bug 1326067 part 2, should have been fixed by bug 1326067 part 5.
#1 crash in Nightly 20170120225350, with 19 occurrences. No Nightly builds have been made for Android since then, as far as I can tell, so no confirmation yet that it's been fixed.
(In reply to Nicholas Nethercote [:njn] from comment #2)
> #1 crash in Nightly 20170120225350, with 19 occurrences. No Nightly builds
> have been made for Android since then, as far as I can tell, so no
> confirmation yet that it's been fixed.

Just to add date (on why no nightlies), last we [releng] enabled taskcluster-generated nightlies. That includes android. We didn't enable the automatic scheduling of them until today (today's was a manual trigger, tomorrows should trigger automatically).

The first taskcluster nightlies are before the first crash date, so is unlikely to be a taskcluster specific issue involved in this bug.
Component: JavaScript Engine → JavaScript Engine: JIT
[Tracking Requested - why for this release]: Nightly Fennec top crash.
Tracking 53+ for this top nightly crash.
Priority: -- → P1
This is no longer very high volume so I'm dropping the tracking flag.
This spike was both caused and fixed by bug 1326067 (see comment 1).
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla53
You need to log in before you can comment on or make changes to this bug.