[wmfme] mfpmp process leaks after playing EME playback
Categories
(Core :: Audio/Video: Playback, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox118 | --- | verified |
People
(Reporter: alwu, Assigned: alwu)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
STR.
- Set the preferences
media.eme.playready.enabled=true
andmedia.wmf.media-engine.enabled=1
- Open another new tab, navigating to the https://refapp.hbbtv.org/dash/test_dashjs_sl3000.html?video=sl2000b
- Open Process Explorer to check whether
mfpmp
process is created - Close the tab containing the test page
Expect.
5. mfpmp
process should disappear
Actual
5. mfpmp
process still exists
Assignee | ||
Comment 1•1 year ago
|
||
I found that the leaking problem actually behaves differently on my Win10 and Win11. On my Win11, bug 1839493 did solve the leaking problem for this test page. But on Win10, the problem still exists...,
Comment 2•1 year ago
|
||
The severity field is not set for this bug.
:jimm, could you have a look please?
For more information, please visit BugBot documentation.
Assignee | ||
Comment 3•1 year ago
|
||
Assignee | ||
Comment 4•1 year ago
|
||
Depends on D186481
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 5•1 year ago
|
||
Depends on D186482
Comment 7•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/1cc302d6f198
https://hg.mozilla.org/mozilla-central/rev/36467382da90
https://hg.mozilla.org/mozilla-central/rev/90da8704edec
Updated•1 year ago
|
Comment 8•1 year ago
|
||
Reproduced the issue with Firefox 117.0a1 (2023-07-10) on Win 10.
The issue is still reproducible using the STR from the description with Firefox 119.0a1 (20230830212731) and Firefox 118.0b2 (20230829180158) on Win 10. The mfpmp process still exists after the tab displaying the test video is closed. Are there any additional steps or something that I'm missing?
Updated•1 year ago
|
Assignee | ||
Comment 9•1 year ago
|
||
Filed bug 1851070 to investigate the problem on Windows 10. But this bug fixes the problem for Windows 11.
Comment 10•1 year ago
|
||
(In reply to Alastor Wu [:alwu] from comment #9)
Filed bug 1851070 to investigate the problem on Windows 10. But this bug fixes the problem for Windows 11.
I can confirm this, the issue is not reproducible anymore on Win 11 x64 with latest Beta 118.0b3. Marking this verified as fixed, since we have Bug 1851070 to address the problem on Win 10.
Updated•1 year ago
|
Description
•