You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
on android platform,when use convertFileSrc method with customized protocol to load local file to gen a video src, when load video, the request header will like range: bytes=0-, when load large video file,this will trigger OOM and crashed, if response with not all file, it will trigger so many same range request,such as range: bytes=123-, and the video could not play. but it work well in http src.
expect the customize protocol can behave as same as normal http src, because the same custmized protocol work well on ios, is there the android webview video load request as same as ios?
Describe the bug
on android platform,when use convertFileSrc method with customized protocol to load local file to gen a video src, when load video, the request header will like range: bytes=0-, when load large video file,this will trigger OOM and crashed, if response with not all file, it will trigger so many same range request,such as range: bytes=123-, and the video could not play. but it work well in http src.
Reproduction
// customized response
http::Response::builder()
.status(code)
.header("Content-Type", get_mime_type(&path))
.header("Connection", "Keep-Alive")
.header("Keep-Alive", "timeout=58")
.header("Accept-Ranges", "bytes")
.header("Last-Modified", last_modified_str)
.header("Content-Length", (byte_range.2).to_string())
.header(
"Content-Range",
format!("bytes {}-{}/{}", byte_range.0, byte_range.1, file_size),
)
.body(data)
.unwrap();
Expected behavior
expect the customize protocol can behave as same as normal http src, because the same custmized protocol work well on ios, is there the android webview video load request as same as ios?
Full
tauri info
outputStack trace
Additional context
No response
The text was updated successfully, but these errors were encountered: