Simple way to reproduce the problem: 1. open up netwerk/test/unit/test_reentrancy.js 2. add a call to |foo();| at the start of the onStartRequest callback 3. SOLO_FILE=test_reentrancy.js make -C objdir/netwerk check-one The test fails since the rest of onStartRequest doesn't run, but there's no indication that an exception was thrown. This is unacceptable, and has caused numerous problems with silent test failures (or pseudo-successes!).
Created attachment 535260 [details] Sample callstack Here's the call stack of the onStartRequest in case anything stands out. The context's exception is cleared within nsWrappedJSClass::CheckForException which is called near the bottom of CallMethod if JS_CallFunctionValue fails.
You need to log in before you can comment on or make changes to this bug.