Closed
Bug 1255626
Opened 8 years ago
Closed 8 years ago
MP4Demuxer gtest will hang if an error occurs.
Categories
(Core :: Audio/Video: Playback, defect)
Core
Audio/Video: Playback
Tracking
()
RESOLVED
FIXED
mozilla48
Tracking | Status | |
---|---|---|
firefox48 | --- | fixed |
People
(Reporter: jya, Assigned: jya)
Details
Attachments
(1 file)
The MP4DemuxerBinding runs the test and then call mTaskQueue->AwaitShutdownAndIdle(); However, in case of error, the task queue is never shutdown.
Assignee | ||
Comment 1•8 years ago
|
||
Review commit: https://reviewboard.mozilla.org/r/39313/diff/#index_header See other reviews: https://reviewboard.mozilla.org/r/39313/
Attachment #8729255 -
Flags: review?(gsquelart)
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → jyavenard
Comment on attachment 8729255 [details] MozReview Request: Bug 1255626: [gtest] Properly shutdown task queue should error occurs. r?gerald https://reviewboard.mozilla.org/r/39313/#review36025 r+ Check-in comment: "should error occurs" -> "should error occur" or "if error occurs". Optional nits: ::: dom/media/gtest/TestMP4Demuxer.cpp:64 (Diff revision 1) > - RefPtr<MP4DemuxerBinding> self = this; > + RefPtr<MP4DemuxerBinding> binding = this; You could move this line down, closer to the DispatchTask, as it wouldn't even be needed in case of an early return (line 79). ::: dom/media/gtest/TestMP4Demuxer.cpp:275 (Diff revision 1) > - [binding, video] () { > + [binding, &video] () { 'video' is a pointer, and you don't modify it in here, so I don't see an advantage in capturing a pointer by reference. Is it because of ArrayLength? But in this context, 'video' comes from a by-value capture in the outer lambda starting at line 270, so again I'm not sure about the difference. But in the end, if it works, who cares? :-)
Attachment #8729255 -
Flags: review?(gsquelart) → review+
Comment 4•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/fddbd0acfb1d
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
You need to log in
before you can comment on or make changes to this bug.
Description
•