Closed
Bug 701124
Opened 14 years ago
Closed 13 years ago
Threadsafe opt shell failures
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: cdleary, Unassigned)
Details
Using --enable-threadsafe and --with-system-nspr I get:
REGRESSIONS
js1_8/extensions/regress-422269.js
js1_8_5/extensions/worker-error.js
js1_8_5/extensions/worker-error-propagation.js
js1_8_5/extensions/worker-fib.js
js1_8_5/extensions/worker-init.js
js1_8_5/extensions/worker-simple.js
js1_8_5/extensions/worker-terminate.js
js1_8_5/extensions/worker-timeout.js
The workers seem to get
Assertion failure: rt->onOwnerThread(), at /moz/mi-to-commit/js/src/jsapi.cpp:6302
which I believe luke recently added. regress-422269 is a leak test that gets screwed up by conservative stack scanning sometimes.
![]() |
||
Comment 1•14 years ago
|
||
Hopefully threadsafe and the conservative stack scanner are both going away.
Comment 2•13 years ago
|
||
Shell workers are gone, so this should be all fixed.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•