This is not happening in the content XHR timeout code, correct? I tried very hard to make sure it wouldn't happen when writing that code, and khuey simply modified my test.
I was afraid of this :-/
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
That doesn't look like the other failures we had: Assertion failure: any, at ../../../js/src/jsgc.cpp:3303
Component: DOM → DOM: Core & HTML
Product: Core → Core
You need to log in before you can comment on or make changes to this bug.