The following testcase asserts on ionmonkey revision 5a04fd69aa09 (run with --ion -n -m), tested on 64 bit: var patterns = new Array(); patterns[0] = ''; test(); function test() { for (i in patterns) { s = patterns[i]; status =(test)(s); } }

Comment on attachment 600297 [details] [diff] [review] fix (since I'm new here) nice choice on naming it "IonActivation" >+ // We need to close all iterators that are open on the stack. >+ while (cx->enumerators != cx->runtime->ionActivation->savedEnumerators()) { >+ Value v = cx->getPendingException(); >+ cx->clearPendingException(); >+ if (js_CloseIterator(cx, cx->enumerators)) >+ cx->setPendingException(v); >+ } I was wondering if we can't factor out this exception-play, either into js_CloseIterator, if there are some callers which don't want that exception behavior, into a function that calls js_CloseIterator called by here and js::Interpret. To minimize patch burden, perhaps this factoring could be landed as a separate patch on m-c? (If you agree and want to do such a patch, can you un-JS_FRIEND_API js_ValueToIterator/js_CloseIterator?)

Comment on attachment 600591 [details] [diff] [review] v2 Righton

Automatically extracted testcase for this bug was committed: https://hg.mozilla.org/mozilla-central/rev/2e891e0db397