Bug 1818630 Comment 18 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I tried to human-fuzz but failed to repro this. The only way I can imagine is to trick BodyStream to call JS involving synchronous XHR via EnqueueNative (AFAIK only piping can do this) while the async iteration is happening, which should be fixed by bug 1818387 if it's even possible.
Revision 1 by
on 
I tried to human-fuzz but failed to repro this. The only way I can imagine is to trick BodyStream to call JS involving synchronous XHR via EnqueueNative (AFAIK only piping can do this, and can unexpectedly close the stream while still reading) while the async iteration is happening, which should be fixed by bug 1818387 if it's even possible.
Revision 2 by
on 
I tried to human-fuzz but failed to repro this. The only way I can imagine is to trick BodyStream to call JS involving synchronous XHR via EnqueueNative (AFAIK only piping can do this, and can unexpectedly close the stream while still reading) while the async iteration is happening, ~~which should be fixed by bug 1818387 if it's even possible.~~

Edit: Sorry, bug 1818387 will fix the crash but not the sudden closing.

Back to Bug 1818630 Comment 18