Bug 1871768 Comment 4 Edit History

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

To understand what happens, it's better to identify which test the leak is from, and enable [`RemoteDecode`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/ipc/RemoteDecodeUtils.h#14) and [`PlatformDecoderModule`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/platforms/PlatformDecoderModule.h#42) LogModules, so we can get some logs from [`RemoteDecoderManager{Parent, Child}`](https://searchfox.org/mozilla-central/search?q=gRemoteDecodeLog&redirect=false) and [`RemoteMediaDataDecoder`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/ipc/RemoteMediaDataDecoder.cpp#17).

The log module can be enabled by setting `logging.RemoteDecode` and `logging.PlatformDecoderModule` to `5`.
To understand what happens, it's better to identify which test the leak is from, and enable [`RemoteDecode`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/ipc/RemoteDecodeUtils.h#14) and [`PlatformDecoderModule`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/platforms/PlatformDecoderModule.h#42) LogModules, so we can get some logs from [`RemoteDecoderManager{Parent, Child}`](https://searchfox.org/mozilla-central/search?q=gRemoteDecodeLog&redirect=false) and [`RemoteMediaDataDecoder`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/ipc/RemoteMediaDataDecoder.cpp#17).

The log module can be enabled by setting `logging.RemoteDecode` and `logging.PlatformDecoderModule` to `4`.
To understand what happens, it's better to identify which test the leak is from, and enable [`RemoteDecode`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/ipc/RemoteDecodeUtils.h#14) and [`PlatformDecoderModule`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/platforms/PlatformDecoderModule.h#42) LogModules, so we can get some logs from [`RemoteDecoderManager{Parent, Child}`](https://searchfox.org/mozilla-central/search?q=gRemoteDecodeLog&redirect=false) and [`RemoteMediaDataDecoder`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/ipc/RemoteMediaDataDecoder.cpp#17). 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.

The log module can be enabled by setting `logging.RemoteDecode` and `logging.PlatformDecoderModule` to `4`.
To understand what happens, it's better to identify which test the leak is from, and enable [`RemoteDecode`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/ipc/RemoteDecodeUtils.h#14) and [`PlatformDecoderModule`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/platforms/PlatformDecoderModule.h#42) LogModules, so we can get some logs from [`RemoteDecoderManager{Parent, Child}`](https://searchfox.org/mozilla-central/search?q=gRemoteDecodeLog&redirect=false) and [`RemoteMediaDataDecoder`](https://searchfox.org/mozilla-central/rev/a46c21ec5559b6d1ac96fcb95bff6885a10bbf99/dom/media/ipc/RemoteMediaDataDecoder.cpp#17). 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.

The log modules can be enabled by setting `logging.RemoteDecode` and `logging.PlatformDecoderModule` to `4`.

Back to Bug 1871768 Comment 4