[StreamProcessor][null] TypeError: Cannot read property 'getContinuousBufferTimeForTargetTime' of null

[clementhoubrecrunchy]

Environment

• The MPD passes the DASH-IF Conformance Tool on https://conformance.dashif.org/
• The stream has correct Access-Control-Allow-Origin headers (CORS)
• There are no network errors such as 404s in the browser console when trying to play the stream
• The issue observed is not mentioned on https://github.com/Dash-Industry-Forum/dash.js/wiki/FAQ
• The issue occurs in the latest reference client on http://reference.dashif.org/dash.js/ and not just on my page

• Link to playable MPD file: -
• Dash.js version: 4.7.4
• Browser name/version: Chromium M56 (Tizen 4.0) and Chromium M76 (Tizen 6.0).
• OS name/version: Tizen 4.0 and Tizen 6.0

Steps to reproduce

This bug is intermittent, it's difficult to reproduce:

• After seeking on some devices like Tizen 4.0 and Tizen 6.0.
• The error Cannot read property 'getContinuousBufferTimeForTargetTime' of null is thrown.

I'm sorry to not be able to add more informations, but I wasn't able to reproduce by myself the issue.

Observed behavior

When this bug occurred, the player starts an infinite loading and never recovers and is not able to play the video.

Console output

[StreamProcessor][null] TypeError: Cannot read property 'getContinuousBufferTimeForTargetTime' of null

Expected behavior

The player should be able to seek correctly and play the video.

More comments

• Is it possible to avoid this error by checking if the StreamProcessor instance is not null before calling any associated methods?
• I also see that getContinuousBufferTimeForTargetTime can return undefined if there is any error in the try/catch. Should it not return in this case NaN.

[dsilhavy]

Can you paste the full log here? There are multiple places in the code where getContinuousBufferTimeForTargetTime is called. I assume the bufferController object is null for some reason but I dont know why this would be the case.

[clementhoubrecrunchy]

Thank you for your reply! Unfortunately, I'm not able to reproduce the bug by myself. I will try anyway to get more informations to help you to find the issue.