FAQ
If the problem is related to FairPlay, have you read the tutorial?
Not applicable
What version of Shaka Player are you using?
5.2.4
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Not tested
Are you using the demo app or your own custom app?
Custom app
What browser and OS are you using?
Windows11. Goolge Chrome Version 151.0.7922.76 (Official Build) (64-bit)
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
No response
What are the manifest and license server URIs?
none
What configuration are you using? What is the output of player.getNonDefaultConfiguration()?
/** Conservative defaults shared by PC and TV Web runtimes. */
export const DEFAULT_SHAKA_CONFIGURATION: Readonly<Record<string, unknown>> = Object.freeze({
abr: {
// Start conservatively, then let ABR promote quality after playback begins.
defaultBandwidthEstimate: 500_000,
switchInterval: 2,
},
manifest: {
disableText: true,
retryParameters: {
maxAttempts: 3,
baseDelay: 500,
backoffFactor: 2,
fuzzFactor: 0.5,
timeout: 15_000,
},
},
streaming: {
// 正常播放时希望向前缓存的总时长。
bufferingGoal: 0,
// 缓冲不足时,至少补到多少秒才继续播放。越大越稳、越容易延迟起播。
rebufferingGoal: 5,
// 播放点后保留的历史缓冲长度。影响内存和回退能力,对首帧影响很小。
bufferBehind: 20,
lowLatencyMode: true,
// 预取分片数量。更高更平滑,但可能与首帧请求竞争。
segmentPrefetchLimit: 1,
startAtSegmentBoundary: false,
inaccurateManifestTolerance: 2,
disableTextPrefetch: true,
liveSync: {
maxPlaybackRate: 1.01,
minPlaybackRate: 0.99,
},
retryParameters: {
maxAttempts: 3,
baseDelay: 500,
backoffFactor: 2,
fuzzFactor: 0.5,
timeout: 15_000,
},
},
drm: {
retryParameters: {
maxAttempts: 3,
baseDelay: 500,
backoffFactor: 2,
fuzzFactor: 0.5,
timeout: 15_000,
},
},
});
What did you do?
play this:
test..zip
- After clearing all configurations in DEFAULT_SHAKA_CONFIGURATION, the problem still persists.
- Rolling back the Shaka version to 4.16.43 does not resolve the issue.
What did you expect to happen?
It is acceptable to throw playback‑related errors; avoid ANR or out‑of‑memory crashes. Normal playback is preferred.
What actually happened?
ANR occurs immediately when testing this video, with an out‑of‑memory alert popping up after a period of waiting. The issue is 100% reproducible.
Are you planning to send a PR to add it?
Yes
FAQ
If the problem is related to FairPlay, have you read the tutorial?
Not applicable
What version of Shaka Player are you using?
5.2.4
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from
main?Not tested
Are you using the demo app or your own custom app?
Custom app
What browser and OS are you using?
Windows11. Goolge Chrome Version 151.0.7922.76 (Official Build) (64-bit)
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
No response
What are the manifest and license server URIs?
none
What configuration are you using? What is the output of
player.getNonDefaultConfiguration()?/** Conservative defaults shared by PC and TV Web runtimes. */
export const DEFAULT_SHAKA_CONFIGURATION: Readonly<Record<string, unknown>> = Object.freeze({
abr: {
// Start conservatively, then let ABR promote quality after playback begins.
defaultBandwidthEstimate: 500_000,
switchInterval: 2,
},
manifest: {
disableText: true,
retryParameters: {
maxAttempts: 3,
baseDelay: 500,
backoffFactor: 2,
fuzzFactor: 0.5,
timeout: 15_000,
},
},
streaming: {
// 正常播放时希望向前缓存的总时长。
bufferingGoal: 0,
// 缓冲不足时,至少补到多少秒才继续播放。越大越稳、越容易延迟起播。
rebufferingGoal: 5,
// 播放点后保留的历史缓冲长度。影响内存和回退能力,对首帧影响很小。
bufferBehind: 20,
lowLatencyMode: true,
// 预取分片数量。更高更平滑,但可能与首帧请求竞争。
segmentPrefetchLimit: 1,
startAtSegmentBoundary: false,
inaccurateManifestTolerance: 2,
disableTextPrefetch: true,
liveSync: {
maxPlaybackRate: 1.01,
minPlaybackRate: 0.99,
},
retryParameters: {
maxAttempts: 3,
baseDelay: 500,
backoffFactor: 2,
fuzzFactor: 0.5,
timeout: 15_000,
},
},
drm: {
retryParameters: {
maxAttempts: 3,
baseDelay: 500,
backoffFactor: 2,
fuzzFactor: 0.5,
timeout: 15_000,
},
},
});
What did you do?
play this:
test..zip
What did you expect to happen?
It is acceptable to throw playback‑related errors; avoid ANR or out‑of‑memory crashes. Normal playback is preferred.
What actually happened?
ANR occurs immediately when testing this video, with an out‑of‑memory alert popping up after a period of waiting. The issue is 100% reproducible.
Are you planning to send a PR to add it?
Yes