Closed
Bug 1022376
Opened 10 years ago
Closed 10 years ago
LoadManager assumes that when a thread exits the runnable, the thread exits (thread leak)
Categories
(Core :: WebRTC, defect)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
mozilla32
People
(Reporter: jesup, Assigned: jesup)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
4.64 KB,
patch
|
jib
:
review+
|
Details | Diff | Splinter Review |
Needless to say, that's not how NewNamedThread/NewThread works, even if you provide an initial event. We've dealt with in the past by having the runnable resend itself to MainThread to kill the thread.
Really we should look at the API for NewThread and in particular the "and provide an event" case. Also, we should consider allowing threads to call Shutdown on themselves, even if behind the scenes (on some OSes?) it has to proxy it to MainThread. But that's a separate question from this bug.
Assignee | ||
Comment 1•10 years ago
|
||
Assignee | ||
Comment 2•10 years ago
|
||
Comment on attachment 8436545 [details] [diff] [review]
Properly shut down LoadMonitor threads
This is a straight pattern on what we did for AudioStream.cpp's Init thread and Crypto's nsCryptoTask.cpp. Ugly but it's the working pattern for now.
Attachment #8436545 -
Flags: review?(jib)
Comment 3•10 years ago
|
||
Comment on attachment 8436545 [details] [diff] [review]
Properly shut down LoadMonitor threads
Review of attachment 8436545 [details] [diff] [review]:
-----------------------------------------------------------------
lgtm.
Attachment #8436545 -
Flags: review?(jib) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Target Milestone: --- → mozilla32
Comment 5•10 years ago
|
||
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Comment 6•10 years ago
|
||
This push backed out for Android crashes during 408431-1.html:
https://tbpl.mozilla.org/?tree=Mozilla-Inbound&jobname=Android%204.0%20Panda%20mozilla-inbound%20opt%20test%20crashtest&fromchange=c66224db3600&tochange=6cc9ac1f57fa
I saw bug 1022235 comment 8 - however the existing 408431-1.html crashes were on other platforms - Android 4.0 debug m-6 was green before, with these two changesets, it isn't.
remote: https://hg.mozilla.org/integration/mozilla-inbound/rev/dc93584a0948
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 7•10 years ago
|
||
Relanded with agreement in IRC from edmorely - bug 1022235 is caused by bug 1022509
https://hg.mozilla.org/integration/mozilla-inbound/rev/97ffe21da653
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → FIXED
Comment 8•10 years ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•