Closed Bug 1269268 Opened 8 years ago Closed 8 years ago

Intermittent leakcheck | default process: 212 bytes leaked (CondVar, Mutex, Runnable, nsTArray_base, nsThread)

Categories

(Core :: WebRTC, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla49
Tracking Status
firefox49 --- fixed

People

(Reporter: cbook, Assigned: khuey)

References

()

Details

(Keywords: intermittent-failure, memory-leak)

Attachments

(1 file)

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: nobody → khuey
Component: General → WebRTC
Attached patch PatchSplinter Review
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)
Attachment #8748952 - Flags: review?(rjesup) → review+
Rank: 25
Priority: -- → P2
https://hg.mozilla.org/mozilla-central/rev/03540c2e61c1
https://hg.mozilla.org/mozilla-central/rev/8353213efc26
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla49
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: