Closed
Bug 1584362
Opened 5 years ago
Closed 5 years ago
Crash in [@ mozilla::net::WebrtcTCPSocket::OnInputStreamReady]
Categories
(Core :: WebRTC: Networking, defect, P2)
Tracking
()
RESOLVED
FIXED
mozilla71
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox67 | --- | unaffected |
firefox68 | --- | unaffected |
firefox69 | --- | unaffected |
firefox70 | --- | unaffected |
firefox71 | --- | fixed |
People
(Reporter: marcia, Assigned: bwc)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
This bug is for crash report bp-5e5a48af-a238-4934-8925-2169a0190921.
Seen while looking at nightly crash stats - macOS 10.14 crashes which started in 20190920094918: https://bit.ly/2n3kGw6
https://ome.tv/ is one URL.
Top 10 frames of crashing thread:
0 XUL mozilla::net::WebrtcTCPSocket::OnInputStreamReady media/mtransport/ipc/WebrtcTCPSocket.cpp:592
1 XUL nsPipeEvents::~nsPipeEvents xpcom/io/nsPipe3.cpp:1131
2 XUL nsPipe::OnPipeException xpcom/io/nsPipe3.cpp:964
3 XUL nsPipeOutputStream::CloseWithStatus xpcom/io/nsPipe3.cpp:1622
4 XUL nsAStreamCopier::Process xpcom/io/nsStreamUtils.cpp:342
5 XUL non-virtual thunk to nsAStreamCopier::Run xpcom/io/nsStreamUtils.cpp
6 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1225
7 XUL NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
8 XUL mozilla::net::nsSocketTransportService::Run netwerk/base/nsSocketTransportService2.cpp:1011
9 XUL non-virtual thunk to mozilla::net::nsSocketTransportService::Run netwerk/base/nsSocketTransportService2.cpp
Assignee | ||
Comment 1•5 years ago
|
||
Might be fixed by bug 1583046.
Comment 2•5 years ago
|
||
Based on when this started and recent code changes, I'm calling this as a regression from bug 1569183. Feel free to update or close if comment 1 pans out.
Assignee | ||
Comment 3•5 years ago
|
||
Not seeing this on crash-stats since bug 1583046 landed, but was very low frequency to begin with, so hard to tell right now if it is fixed yet. Will probably have to wait a week or two.
Comment 4•5 years ago
|
||
Still no crashes a week later, let's call this fixed?
Status: NEW → RESOLVED
Closed: 5 years ago
Depends on: 1583046
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Updated•5 years ago
|
Assignee: nobody → docfaraday
status-firefox67:
--- → unaffected
status-firefox68:
--- → unaffected
status-firefox69:
--- → unaffected
status-firefox-esr60:
--- → unaffected
status-firefox-esr68:
--- → unaffected
Updated•5 years ago
|
Flags: qe-verify+
Updated•3 years ago
|
Has Regression Range: no → yes
You need to log in
before you can comment on or make changes to this bug.
Description
•