Closed
Bug 1583046
Opened 5 years ago
Closed 5 years ago
Crash in [@ mozilla::net::WebrtcTCPSocket::OpenWithoutHttpProxy]
Categories
(Core :: WebRTC: Networking, defect, P2)
Tracking
()
RESOLVED
FIXED
mozilla71
Tracking | Status | |
---|---|---|
firefox-esr60 | --- | unaffected |
firefox-esr68 | --- | unaffected |
firefox69 | --- | unaffected |
firefox70 | --- | unaffected |
firefox71 | --- | fixed |
People
(Reporter: jseward, Assigned: bwc)
References
Details
(Keywords: crash)
Crash Data
Attachments
(1 file)
This bug is for crash report bp-fe032e69-2b37-4bf9-9a0a-7b2250190921.
This occurs in two different installations of the Windows nightly of 20190919094654.
Top 10 frames of crashing thread:
0 xul.dll nsresult mozilla::net::WebrtcTCPSocket::OpenWithoutHttpProxy media/mtransport/ipc/WebrtcTCPSocket.cpp:314
1 xul.dll nsresult mozilla::net::WebrtcTCPSocket::OnProxyAvailable media/mtransport/ipc/WebrtcTCPSocket.cpp
2 xul.dll static nsresult mozilla::net::nsAsyncResolveRequest::DoCallback::<unnamed-tag>::operator netwerk/base/nsProtocolProxyService.cpp:366
3 xul.dll xul.dll@0xac6995
4 xul.dll nsresult mozilla::net::nsAsyncResolveRequest::AsyncApplyFilters::Finish netwerk/base/nsProtocolProxyService.cpp:599
5 xul.dll nsresult mozilla::net::nsAsyncResolveRequest::AsyncApplyFilters::ProcessNextFilter netwerk/base/nsProtocolProxyService.cpp:509
6 xul.dll nsresult mozilla::net::nsAsyncResolveRequest::AsyncApplyFilters::AsyncProcess netwerk/base/nsProtocolProxyService.cpp:485
7 xul.dll void mozilla::net::nsAsyncResolveRequest::DoCallback netwerk/base/nsProtocolProxyService.cpp:375
8 xul.dll nsresult mozilla::net::ExecuteCallback::Run netwerk/base/nsPACMan.cpp:119
9 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1225
Reporter | ||
Updated•5 years ago
|
Flags: needinfo?(docfaraday)
Assignee | ||
Comment 1•5 years ago
|
||
Maybe this is another manifestation of bug 1582646?
Flags: needinfo?(docfaraday)
Updated•5 years ago
|
Component: Networking → WebRTC: Networking
Comment 2•5 years ago
|
||
If Byron's thought is true in comment 1, we should see reports fall starting with the next build since the fix for Bug 1582646 just landed.
Updated•5 years ago
|
Priority: -- → P2
Assignee | ||
Comment 3•5 years ago
|
||
I think I might see some additional issues stemming from the fact that the proxy lookup callback isn't happening on the thread we asked it to happen on. I'm working on a fix.
Assignee: nobody → docfaraday
Assignee | ||
Comment 4•5 years ago
|
||
Assignee | ||
Comment 5•5 years ago
|
||
Assignee | ||
Comment 6•5 years ago
|
||
Try looks fine.
Assignee | ||
Comment 7•5 years ago
|
||
Manual testing of proxy stuff (including secure-proxy) looks fine.
Pushed by bcampen@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/44cb42559383
Tighten down threading rules. r=mjf
Comment 9•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Updated•5 years ago
|
status-firefox69:
--- → unaffected
status-firefox70:
--- → unaffected
status-firefox-esr60:
--- → unaffected
status-firefox-esr68:
--- → unaffected
You need to log in
before you can comment on or make changes to this bug.
Description
•