Closed
Bug 1269268
Opened 9 years ago
Closed 9 years ago
Intermittent leakcheck | default process: 212 bytes leaked (CondVar, Mutex, Runnable, nsTArray_base, nsThread)
Categories
(Core :: WebRTC, defect, P2)
Core
WebRTC
Tracking
()
RESOLVED
FIXED
mozilla49
Tracking | Status | |
---|---|---|
firefox49 | --- | fixed |
People
(Reporter: cbook, Assigned: khuey)
References
()
Details
(Keywords: intermittent-failure, memory-leak)
Attachments
(1 file)
2.15 KB,
patch
|
jesup
:
review+
|
Details | Diff | Splinter Review |
00:59:55 WARNING - TEST-UNEXPECTED-FAIL | leakcheck | default process: 212 bytes leaked (CondVar, Mutex, Runnable, nsTArray_base, nsThread)
https://treeherder.mozilla.org/logviewer.html#?job_id=27032481&repo=mozilla-inbound
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → khuey
Component: General → WebRTC
Assignee | ||
Comment 1•9 years ago
|
||
The bug here is that the calling thread is already shut down by the time we try to come back to it to call nsIThread::Shutdown on the camera thread. The calling thread is a chromium thread, so the nsThread for it is automatically created by the thread manager and will accept events even when there's no chance that they will ever run so we get the leak.
Thankfully, we can just shut down the camera thread from a thread we know will be alive.
Attachment #8748952 -
Flags: review?(rjesup)
Assignee | ||
Updated•9 years ago
|
Attachment #8748952 -
Attachment is patch: true
Updated•9 years ago
|
Attachment #8748952 -
Flags: review?(rjesup) → review+
Updated•9 years ago
|
Rank: 25
Priority: -- → P2
Comment 4•9 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/03540c2e61c1
https://hg.mozilla.org/mozilla-central/rev/8353213efc26
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox49:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
You need to log in
before you can comment on or make changes to this bug.
Description
•