Closed Bug 947912 Opened 11 years ago Closed 10 years ago

Assertion failure: !enabled(), at ../vm/SPSProfiler.cpp:43

Categories

(Core :: JavaScript Engine, defect)

x86_64
Linux
defect
Not set
critical

Tracking

()

RESOLVED FIXED
mozilla31

People

(Reporter: decoder, Assigned: jld)

References

Details

(Keywords: assertion, testcase, Whiteboard: [jsbugmon:])

Attachments

(1 file, 1 obsolete file)

The following testcase asserts on mozilla-central revision 0204febd3146 (run with --fuzzing-safe --ion-eager):


for (var i = 0; i < 2; ++i) {
    function g() {
	enableSPSProfilingAssertions(false)
    }
    g();
}
Whiteboard: [jsbugmon:update]
Assignee: general → nobody
QA Contact: general
Attachment #8344626 - Attachment is obsolete: true
Whiteboard: [jsbugmon:update] → [jsbugmon:update,ignore]
JSBugMon: The testcase found in this bug no longer reproduces (tried revision 5b6e82e7bbbf).
Whiteboard: [jsbugmon:update,ignore] → [jsbugmon:bisectfix]
Whiteboard: [jsbugmon:bisectfix] → [jsbugmon:]
JSBugMon: Fix Bisection requested, result:
=== Tinderbox Build Bisection Results by autoBisect ===

The "bad" changeset has the timestamp "20140327191048" and the hash "6ea0bf2b69f0".
The "good" changeset has the timestamp "20140327192149" and the hash "d9dc1a7d4649".

Likely fix window: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=6ea0bf2b69f0&tochange=d9dc1a7d4649
Did bug 914561 maybe fix this?
Flags: needinfo?(jld)
Yes, it did.  I ran into this assertion while writing test cases for bug 914561, and changed EnableSPSProfilingAssertions to disable the profiler first (if it was enabled) before setting the stack.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(jld)
Resolution: --- → FIXED
Assignee: nobody → jld
Depends on: 914561
Target Milestone: --- → mozilla31
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: