1654337 - Crash in [@ <name omitted> | mozilla::net::FailDelayManager::Add]

Status: RESOLVED WORKSFORME

(Core :: DOM: Networking, defect, P5)

Description

[Jessie [:jbonisteel] pls NI]

Just happened upon this crash, figured I should file a bug for it

This bug is for crash report bp-52d58368-9e9f-4314-9710-ca0950200721.

Top 10 frames of crashing thread:

0 XUL <name omitted> xpcom/string/nsTSubstring.cpp:456
1 XUL mozilla::net::FailDelayManager::Add netwerk/protocol/websocket/WebSocketChannel.cpp:193
2 XUL mozilla::net::nsWSAdmissionManager::OnStopSession netwerk/protocol/websocket/WebSocketChannel.cpp:391
3 XUL mozilla::net::WebSocketChannel::DoStopSession netwerk/protocol/websocket/WebSocketChannel.cpp:2303
4 XUL non-virtual thunk to mozilla::net::WebSocketChannel::OnError netwerk/protocol/websocket/WebSocketChannel.cpp
5 XUL mozilla::net::nsWebSocketConnection::OnInputStreamReady netwerk/protocol/websocket/nsWebSocketConnection.cpp
6 XUL nsInputStreamReadyEvent::Run xpcom/io/nsStreamUtils.cpp:94
7 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1234
8 XUL NS_ProcessPendingEvents xpcom/threads/nsThreadUtils.cpp:461
9 XUL mozilla::net::nsSocketTransportService::Run netwerk/base/nsSocketTransportService2.cpp:1247

Comment 1

[Andy Grover [:grover]]

This only has happened once, and the code in question looks pretty innocent. I'm wondering if some other problem could have indirectly caused the heap allocator to become corrupted or something? Let's see if we get any more instances of this crash.

Comment 2

[Vicky Chin [:vchin]]

Is this really an S1 bug?

Comment 3

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.