Comment 9 for bug 1914147

Revision history for this message
In , Dtownsend (dtownsend) wrote :

Based on the stack info it looks like maybe Firefox was stuck in a deadlock somewhere in the HTTP code so moving this over there for mre investigation. Is this still occurring?