Closed Bug 977953 Opened 10 years ago Closed 10 years ago

Epic Citadel crashes with dirty profile

Categories

(Core :: JavaScript Engine, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 977538
Tracking Status
firefox29 --- affected
firefox30 --- affected

People

(Reporter: ferongr, Unassigned)

References

()

Details

(Keywords: crash, regression, Whiteboard: [js:p1])

Attachments

(1 file)

Attached file about:support contents
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 ID:20140227030203 CSet: a98a1d78817f 
2014-02-27 Nightly build

The Epic Citadel demo crashes with my regular Nightly profile. It's not extension related since it still crashes with all extensions disabled. It crashes after loading finishes, when the progressbar starts filling second time.

Example crash IDs:
bp-ccaf12f4-ece8-4f12-9377-280d32140228
bp-b0aee88a-c869-4cdd-9ff9-96b9a2140228

I managed to get a regression range using mozregression and using my profile.

Last good revision: 5c7fa2bfea8b (2013-12-19)
First bad revision: c9ea463d36c3 (2013-12-20)
Pushlog: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5c7fa2bfea8b&tochange=c9ea463d36c

Also attaching about:support contents. I'd be happy to provide my profile folder to a Mozilla developer if needed.
Looks like JIT crashes?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(jdemooij)
Keywords: regression
Reporter, are you willing to try using builds from http://inbound-archive.pub.build.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/ to further narrow the regression range?  We seem to have those back to September, though finding the ones for a particular date is a bit annoying.  :(
I'll get on it (mozregression tried to bisect inbound for me but it stalled).
This looks a lot like a bug I fixed yesterday. The patch should be in the next Nightly, would you mind giving it a try once it's out?
Some time (30mins) before filing this bug I tried the last green build linked from tbpl and it also failed. In any case, I will try the next Nightly ofcourse.
(If I'm right, only one of them should crash. If they both crash it's another bug.)
4cfb6c61b137 bad
58eca03214a6 good

You were right jandem. Thanks for saving me some frustration trying to bisect inbound :)
The new Nightly is out and the underlying but is fixed. WFM or DUPE?
Does this bug affect 29 ? (the tracking was requested for 29)
Keywords: crash
Whiteboard: [js:p1]
So was this fixed by bug 977538?
Yup.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(jdemooij)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: