Bug 1871768 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to C.M.Chang[:chunmin] from comment #4)
> To understand what happens, it's better to identify which test the leak is from

It looks like the leak is from videoFrame-createImageBitmap.https.any.js. If it's disabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=42e1c3be923966b4ee08c81fed8596a997549659&selectedTaskRun=DPzosCrUQCaxKGmA9g0cyg.0
the the error is gone. Additionally, there is a leak log. See: Bug 1872311 comment #1
Revision 1 by
on 
(In reply to C.M.Chang[:chunmin] from comment #4)
> To understand what happens, it's better to identify which test the leak is from

It looks like the leak is from videoFrame-createImageBitmap.https.any.js. If it's disabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=42e1c3be923966b4ee08c81fed8596a997549659&selectedTaskRun=DPzosCrUQCaxKGmA9g0cyg.0
then the error is gone. Additionally, there is a leak log. See: Bug 1872311 comment #1

>  Besides, adding a log in ~VideoDecoder might help to see if there is any pending video decoder in the wpt since some tests don't call `.close()` explicitly.

Neither encoder.close() nor decoder.close() is called in videoFrame-createImageBitmap.https.any.js, so I guess the shutdown-ticket is not released and the ticket blocks the rdd shutdown.
Revision 2 by
on 
(In reply to C.M.Chang[:chunmin] from comment #4)
> To understand what happens, it's better to identify which test the leak is from

It looks like the leak is from videoFrame-createImageBitmap.https.any.js. If it's disabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=42e1c3be923966b4ee08c81fed8596a997549659&selectedTaskRun=DPzosCrUQCaxKGmA9g0cyg.0
then the error is gone. Additionally, there is a leak log: Bug 1872311 comment #1

>  Besides, adding a log in ~VideoDecoder might help to see if there is any pending video decoder in the wpt since some tests don't call `.close()` explicitly.

Neither encoder.close() nor decoder.close() is called in videoFrame-createImageBitmap.https.any.js, so I guess the shutdown-ticket is not released and the ticket blocks the rdd shutdown.
Revision 3 by
on 
(In reply to C.M.Chang[:chunmin] from comment #4)
> To understand what happens, it's better to identify which test the leak is from

It looks like the leak is from videoFrame-createImageBitmap.https.any.js. If it's disabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=42e1c3be923966b4ee08c81fed8596a997549659&selectedTaskRun=DPzosCrUQCaxKGmA9g0cyg.0
then the error is gone. Additionally, there is a leak log: Bug 1872311 comment #1

>  Besides, adding a log in ~VideoDecoder might help to see if there is any pending video decoder in the wpt since some tests don't call `.close()` explicitly.

Neither `encoder.close()` nor `decoder.close()` is called in videoFrame-createImageBitmap.https.any.js, so I guess the shutdown-ticket is not released and the ticket blocks the rdd shutdown.
Revision 4 by
on 
(In reply to C.M.Chang[:chunmin] from comment #4)
> To understand what happens, it's better to identify which test the leak is from

It looks like the leak is from videoFrame-createImageBitmap.https.any.js. If it's disabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=42e1c3be923966b4ee08c81fed8596a997549659&selectedTaskRun=DPzosCrUQCaxKGmA9g0cyg.0
then the error is gone. Additionally, there is a leak log: Bug 1872311 comment #1

>  Besides, adding a log in ~VideoDecoder might help to see if there is any pending video decoder in the wpt since some tests don't call `.close()` explicitly.

Neither `encoder.close()` nor `decoder.close()` is called in videoFrame-createImageBitmap.https.any.js, so I guess the shutdown-ticket is not released and the ticket blocks the rdd shutdown.

The logs for the test is here: https://treeherder.mozilla.org/logviewer?job_id=442058969&repo=try&lineNumber=5158-5276
Revision 5 by
on 
(In reply to C.M.Chang[:chunmin] from comment #4)
> To understand what happens, it's better to identify which test the leak is from

It looks like the leak is from videoFrame-createImageBitmap.https.any.js. If it's disabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=42e1c3be923966b4ee08c81fed8596a997549659&selectedTaskRun=DPzosCrUQCaxKGmA9g0cyg.0
then the error is gone. Additionally, there is a leak log: Bug 1872311 comment #1

>  Besides, adding a log in ~VideoDecoder might help to see if there is any pending video decoder in the wpt since some tests don't call `.close()` explicitly.

Neither `encoder.close()` nor `decoder.close()` is called in videoFrame-createImageBitmap.https.any.js, so I guess the shutdown-ticket is not released and the ticket blocks the rdd shutdown.

The logs (enabled by [this pref](https://hg.mozilla.org/try/rev/b95a64779fd5a25f26a6722519265634e51513d9)) for the test is here: https://treeherder.mozilla.org/logviewer?job_id=442058969&repo=try&lineNumber=5158-5276
Revision 6 by
on 
(In reply to C.M.Chang[:chunmin] from comment #4)
> To understand what happens, it's better to identify which test the leak is from

It looks like the leak is from videoFrame-createImageBitmap.https.any.js. If it's disabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=42e1c3be923966b4ee08c81fed8596a997549659&selectedTaskRun=DPzosCrUQCaxKGmA9g0cyg.0
then the error is gone. Additionally, there is a leak log: Bug 1872311 comment #1

>  Besides, adding a log in ~VideoDecoder might help to see if there is any pending video decoder in the wpt since some tests don't call `.close()` explicitly.

Neither `encoder.close()` nor `decoder.close()` is called in videoFrame-createImageBitmap.https.any.js, so I guess the shutdown-ticket is not released and the ticket blocks the rdd shutdown.

The logs (enabled by [these prefs](https://hg.mozilla.org/try/rev/b95a64779fd5a25f26a6722519265634e51513d9)) for the test is here: https://treeherder.mozilla.org/logviewer?job_id=442058969&repo=try&lineNumber=5158-5276
Revision 7 by
on 
(In reply to C.M.Chang[:chunmin] from comment #4)
> To understand what happens, it's better to identify which test the leak is from

It looks like the leak is from videoFrame-createImageBitmap.https.any.js. If it's disabled:
https://treeherder.mozilla.org/jobs?repo=try&revision=42e1c3be923966b4ee08c81fed8596a997549659&selectedTaskRun=DPzosCrUQCaxKGmA9g0cyg.0
then the error is gone. Additionally, there is a leak log: Bug 1872311 comment #1

>  Besides, adding a log in ~VideoDecoder might help to see if there is any pending video decoder in the wpt since some tests don't call `.close()` explicitly.

Neither `encoder.close()` nor `decoder.close()` is called in videoFrame-createImageBitmap.https.any.js, maybe shutdown-ticket is not released and the ticket blocks the rdd shutdown?

The logs (enabled by [these prefs](https://hg.mozilla.org/try/rev/b95a64779fd5a25f26a6722519265634e51513d9)) for the test is here: https://treeherder.mozilla.org/logviewer?job_id=442058969&repo=try&lineNumber=5158-5276

Back to Bug 1871768 Comment 6