Closed Bug 760044 Opened 13 years ago Closed 7 years ago

crash in js::ToStringSlow

Categories

(Core :: JavaScript Engine, defect)

14 Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED WONTFIX

People

(Reporter: cbook, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [js:inv:p3])

Crash Data

This bug was filed from the Socorro interface and is report bp-140198a9-d026-4775-9513-8ef072120530 . ============================================================= found on the Firefox 14a2 Crash Report - no comments so far Crashing Thread Frame Module Signature Source 0 mozjs.dll js::ToStringSlow js/src/jsstr.cpp:3289 1 mozjs.dll js::NativeIterator::allocateIterator js/src/jsiter.cpp:554 2 mozjs.dll VectorToKeyIterator js/src/jsiter.cpp:602 3 mozjs.dll js::EnumeratedIdVectorToIterator js/src/jsiter.cpp:671 4 mozjs.dll js::ProxyHandler::iterate js/src/jsproxy.cpp:284 5 mozjs.dll js::Proxy::iterate js/src/jsproxy.cpp:905 6 mozjs.dll js::GetIterator js/src/jsiter.cpp:780 7 mozjs.dll js::ValueToIterator js/src/jsiter.cpp:919 8 mozjs.dll js::Interpret js/src/jsinterp.cpp:2071 9 mozjs.dll js::ContextStack::pushInvokeFrame js/src/vm/Stack.cpp:783 10 mozjs.dll js::InvokeKernel js/src/jsinterp.cpp:535 11 mozjs.dll mozjs.dll@0x8cbf
Whiteboard: [js:p1:fx16]
Whiteboard: [js:p1:fx16] → [js:inv:p3]
We have a related Firebug report plus reproducible test case: http://code.google.com/p/fbug/issues/detail?id=5712 Sebastian
I tested right now with the Beta, Aurora and Nightly versions of Firefox and it seems to be already fixed in Aurora and Nightly. Sebastian
If somebody considers this to fix this for Firefox 14, there's a simplified test case described in http://code.google.com/p/fbug/issues/detail?id=5751. Sebastian
Assignee: general → nobody
Crash Signature: [@ js::ToStringSlow(JSContext*, JS::Value const&)] → [@ js::ToStringSlow(JSContext*, JS::Value const&)] [@ js::ToStringSlow]
Closing because no crashes reported for 12 weeks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.