Closed
Bug 1668592
Opened 4 years ago
Closed 4 years ago
Crash in [@ nsPipeInputStream::ReadSegments]
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
RESOLVED
DUPLICATE
of bug 1673186
People
(Reporter: sefeng, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/be8ba891-4543-4623-a331-8df2a0200929
Reason: SIGSEGV /SEGV_MAPERR
MOZ_CRASH Reason: MOZ_DIAGNOSTIC_ASSERT(!mReadState.mActiveRead)
Top 10 frames of crashing thread:
0 libxul.so nsPipeInputStream::ReadSegments xpcom/io/nsPipe3.cpp:1314
1 libxul.so nsInputStreamPump::PeekStream netwerk/base/nsInputStreamPump.cpp:104
2 libxul.so nsBaseChannel::OnStartRequest netwerk/base/nsBaseChannel.cpp:826
3 libxul.so nsInputStreamPump::OnInputStreamReady netwerk/base/nsInputStreamPump.cpp:390
4 libxul.so nsInputStreamReadyEvent::Run xpcom/io/nsStreamUtils.cpp:94
5 libxul.so mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal xpcom/threads/TaskController.cpp:514
6 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1234
7 libxul.so mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:87
8 libxul.so MessageLoop::Run ipc/chromium/src/base/message_loop.cc:309
9 libxul.so nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
I only see one crash from this signature, however, this seems like a valid crash.
This spiked in build 20201024094139 (pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=1980f87855fc557e7ef6bb24b66c4d2df5606afa&tochange=78130fed97b782e51d3da1ce1395a2bdb2d83db4).
Comment 2•4 years ago
|
||
Hi Valentin, any idea what might be going on here?
Component: XPCOM → Networking
Flags: needinfo?(valentin.gosu)
Updated•4 years ago
|
Updated•4 years ago
|
Has Regression Range: --- → yes
Comment 3•4 years ago
|
||
Seems the same as bug 1673186.
Status: NEW → RESOLVED
Closed: 4 years ago
Flags: needinfo?(valentin.gosu)
Resolution: --- → FIXED
See Also: → 1673186
Updated•4 years ago
|
Flags: needinfo?(mconley)
Resolution: FIXED → DUPLICATE
Updated•3 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•