hawm
(Hawm)
December 7, 2023, 4:16am
1
Paste an mp4 video direct link into the composer and then will be onebox as video, and post it.
Then play the video, check the network on devtools, will see huge data transfer. For example, a 100MB video will transfer about 1GB of data. Seems the service worker caused it.
1 Like
Can you please put an example on try.discourse.org ?
1 Like
I do see this:
Note this 31,539,436B video has had most of the content requested multiple times in several requests:
Content-Length: 31539436
Content-Range: bytes 0-31539435/31539436
Content-Length: 180460
Content-Range: bytes 31358976-31539435/31539436
Content-Length: 31506668
Content-Range: bytes 32768-31539435/31539436
Content-Length: 31375596
Content-Range: bytes 163840-31539435/31539436
which match what was requested.
I know this is something we’ve been actively working on improving lately; I’ll ensure the right team is aware.
2 Likes
hawm
(Hawm)
December 7, 2023, 5:54am
4
can you please test my deleted reply on the same topic? view the history play the deleted embedded video and try to manipulate the progress bar.
which really cost a lot of data transfer from my cloud storage
blake
(Blake Erickson)
December 18, 2023, 1:29pm
6
A fix for this has been released. Thanks for reporting @hawm .
discourse:main
← discourse:fix-video-sw
opened 08:05PM - 15 Dec 23 UTC
This bug appears to only be on Chrome due to the service worker fetching
the vid… eo content on page load instead of on play. For some reason
though the service worker would fetch around 4x more than the size of
the video resulting in excessive data being downloaded especially for
larger videos.
meta https://meta.discourse.org/t/287817
internal /t/111387/52
7 Likes
pmusaraj
(Penar Musaraj)
Closed
December 21, 2023, 3:00pm
7
This topic was automatically closed after 3 days. New replies are no longer allowed.