Closed
Bug 710947
Opened 12 years ago
Closed 12 years ago
Assertion failure: !rt->gcRunning, at jsgc.cpp:2083
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla11
People
(Reporter: decoder, Assigned: billm)
References
Details
(Keywords: assertion, testcase, Whiteboard: js-triage-needed)
Attachments
(1 file)
1.08 KB,
patch
|
luke
:
review+
|
Details | Diff | Splinter Review |
The following test asserts on mozilla-central revision 41f75cbb91f2 (options -m -n -a): function startTest() { if (typeof document != "object" || !document.location.href.match(/jsreftest.html/)) {} }; gczeal(4); startTest(); ArrayBuffer( 946684800000 ); Not S-s due to incremental gc.
Assignee | ||
Updated•12 years ago
|
Assignee: general → wmccloskey
Assignee | ||
Comment 1•12 years ago
|
||
This is the problem we talked about a while ago where we remove an entry from a hashtable during GC. The remove method calls malloc, which can trigger a GC. I just turned the assert into a condition. Ideally we wouldn't malloc during GC, but this fix is safe and the fix to HashMap::remove would be annoying and not really necessary.
Attachment #582365 -
Flags: review?(luke)
![]() |
||
Updated•12 years ago
|
Attachment #582365 -
Flags: review?(luke) → review+
Assignee | ||
Comment 2•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/9d6469ffd577
Target Milestone: --- → mozilla11
Comment 3•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/9d6469ffd577
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•11 years ago
|
||
A testcase for this bug was automatically identified at js/src/jit-test/tests/basic/bug710947.js.
Flags: in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•