Closed Bug 1644065 Opened 5 years ago Closed 4 years ago

Crash in [@ mozilla::net::nsHttpTransaction::nsHttpTransaction]

Categories

(Core :: Networking: HTTP, defect, P1)

Unspecified
All
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: gsvelto, Assigned: kershaw)

References

Details

(Keywords: crash, Whiteboard: [necko-triaged])

Crash Data

This bug is for crash report bp-1c28cc99-bbfa-42b8-868d-ca1c20200605.

Top 10 frames of crashing thread:

0 XUL mozilla::net::nsHttpTransaction::nsHttpTransaction netwerk/protocol/http/nsHttpTransaction.cpp:148
1 XUL mozilla::net::HttpTransactionChild::RecvInit netwerk/protocol/http/HttpTransactionChild.cpp:183
2 XUL mozilla::net::PHttpTransactionChild::OnMessageReceived ipc/ipdl/PHttpTransactionChild.cpp:563
3 XUL mozilla::net::PSocketProcessChild::OnMessageReceived ipc/ipdl/PSocketProcessChild.cpp:1760
4 XUL mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2166
5 XUL mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1969
6 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1236
7 XUL mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
8 XUL MessageLoop::Run ipc/chromium/src/base/message_loop.cc:290
9 XUL nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137

This is a NULL pointer access, probably to the gHttpHandler variable. Disregard the crashes under this signature that are not in the nightly channel because they're unrelated. This seems to have started in buildid 20200526213752 and happens on both Windows and macOS.

Bug 1643515 is a crash involving HttpTransactionParent that also first appeared in the 20200526213752 build. I wonder if they are related.

See Also: → 1643515

This patch should be able to fix this.

Assignee: nobody → kershaw
Severity: -- → S3
Priority: -- → P1
Whiteboard: [necko-triaged]

This crash in occurs in FF 78 when network.process.enabled and network.http.network_access_on_socket_process.enabled are both set to true. It immediately crashes at startup, so you have to back and set them to false from prefs.js.

This is fixed by the patch in comment #2.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.