Closed
Bug 466265
Opened 16 years ago
Closed 15 years ago
Assertion failure: cx->operationLimit > 0, at ../jscntxt.cpp:1383
Categories
(Core :: JavaScript Engine, defect, P2)
Tracking
()
RESOLVED
INVALID
mozilla1.9.1
People
(Reporter: bc, Unassigned)
References
Details
(Keywords: crash, regression, testcase, Whiteboard: fixed by newer patch in 453157)
Attachments
(1 file)
765 bytes,
patch
|
Details | Diff | Splinter Review |
mozilla-central Every js test fails in the shell with this assertion: Assertion failure: cx->operationLimit > 0, at ../jscntxt.cpp:1383 example test: e4x/Expressions/11.1.1.js regression changeset: 21857:8329a91db67d user: Andrei Saprykin <andrei@runitsoft.com> date: Thu Nov 20 22:25:34 2008 +0100 summary: bug 453157 - watchdog thread as an alternative to operation count. r=igor,mrbkap a1.9.0b2=beltzner *** revision 8329a91db67d found ***
Flags: in-testsuite+
Flags: in-litmus-
Flags: blocking1.9.1?
Comment 1•16 years ago
|
||
I should have seen this when reviewing the patches for bug 453157 - the assert is completely bogus (juts see the assert above it). This affects only single-threaded debug builds.
Assignee: general → igor
Updated•16 years ago
|
Flags: blocking1.9.1? → blocking1.9.1+
Whiteboard: fixed by newer patch in 453157
Target Milestone: mozilla1.9.1b2 → mozilla1.9.1
Updated•16 years ago
|
Priority: -- → P2
Comment 2•16 years ago
|
||
Igor, is this ready to go?
Comment 3•16 years ago
|
||
Or is bug 453157 fixed?
Comment 4•16 years ago
|
||
This bug is a leftover of an attempt to land the watchdog patch. I am not sure how to deal with it - the watchdog patches has long been fixed but since the bug 453157 is not fixed, should I just mark it as works-for-me?
Comment 6•15 years ago
|
||
The offending code doesn't exist any more.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•