Closed
Bug 1107886
Opened 10 years ago
Closed 10 years ago
Assertion failure: isLowered(), at c:\Users\mozilla\debug-builds\mozilla-central\js\src\jit/MIR.h:716
Categories
(Core :: JavaScript Engine: JIT, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cbook, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: assertion)
Attachments
(1 file)
|
(deleted),
text/plain
|
Details |
Found via Bughunter
Steps to reproduce:
-> Load http://www.portafontium.cz/iipimage/30069077/susice-10_3520-o?x=225&y=394&w=416&h=182 in Win7 Trunk Debug Build
--> Assertion failure: isLowered(), at c:\Users\mozilla\debug-builds\mozilla-central\js\src\jit/MIR.h:716
|
Reporter | |
Comment 1•10 years ago
|
||
|
||
Comment 2•10 years ago
|
||
Dan, is this reg allocator related and something you could look at? Thanks.
Flags: needinfo?(sunfish)
|
||
Comment 3•10 years ago
|
||
Judging by the attached debug data, buildSnapsnot is iterating over the recover info for a resume point, and it's trying to use a value which has not yet been lowered.
|
||
Comment 4•10 years ago
|
||
I wonder if this could be related to the Sink algorithm, which is now disabled on inbound / aurora.
I will try to reproduce it tomorrow.
|
|
||
Comment 5•10 years ago
|
||
If this bug cannot be reproduced, then this is likely to be a duplicate of Bug 1108413.
Blocks: 1109195
|
|
||
Comment 7•10 years ago
|
||
(In reply to David Bolter [:davidb] from comment #6)
> Nicolas were you able to repro?
I have not even tried, as the timing and the stack trace are extremely likely to be related to the Sink algorithm issue, which is now fixed.
Does it still fail?
Flags: needinfo?(nicolas.b.pierron)
|
||
Updated•10 years ago
|
Flags: needinfo?(sunfish) → needinfo?(cbook)
|
|
||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
|
|
Reporter | |
Updated•10 years ago
|
Flags: needinfo?(cbook)
|
||
Updated•9 years ago
|
Group: core-security → core-security-release
|
|
||
Updated•7 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•