Frontend memory leak on client devices with livestreams

[tuxayo]

• go to https://invidio.us/watch?v=F0IbjVq-fgs&hl=en-US&local=false&autoplay=0&subtitles=eo
• listen for one hour or more
• close the tab
• in my case I got 1718 MiB of RAM freed
  (I forgot to reopen the tab to measure only the additional RAM after the hour of runtime)

OS: Solus
Browser: Firefox 68.0b14

[tuxayo]

I'll retry on Firefox stable and Chromium.
And maybe report and issue to Mozilla, about:memory and about:performance couldn't see the actual RAM usage.

about:memory showed and error message on the process that was hosting the invidious tab.
So maybe it's and upstream issue.

[tuxayo]

(meanwhile if someone else can reproduce that would be a good help)

[Perflyst]

I can clearly reproduce this issue in Chromium version 75.0.3770.90

It used around 1.6GB RAM after 1 hour. After 1 hour and 17 minutes the tab crashed.

[omarroth]

I expect this is videojs/video.js#5973. #235 may also be relevant.

I haven't kept a tab open long enough to reproduce a crash, but I do observe constant increase in memory on Chrome 75.0.3770.100.

Hopefully there's some more information that can be provided that'll be helpful for the videojs folks. I have a similar heap snapshot to the linked issue, so I believe this is the same issue:

[AlexMV12]

Well, I win the prize for more RAM used! :D

I can confirm this bug. It's not the first time, and I saw it happen both on a self-hosted instance and on third parties instances.

In my case I have Firefox and Archlinux.
In the moment I made the screenshot, the tab was hanging: even refreshing it, nothing would happen, and the graphic was broken (as you can see). However, Firefox was still responsive.

The next time it happens I will try to look into the console.

[Prendeon]

Still relevant on Firefox: 73.0.1 and OS: Manjaro, although i don't have anything to add to what has already been mentioned.

[SamantazFox]

Is that issue still relevant? We've updated multiple times videoJS since then, so should be fixed by now.

[unixfox]

Is that issue still relevant? We've updated multiple times videoJS since then, so should be fixed by now.

Probably, videojs/video.js#5973 is still opened at videojs.

[matthewmcgarvey]

They never scheduled time 😢

[github-actions]

This issue has been automatically marked as stale and will be closed in 30 days because it has not had recent activity and is much likely outdated. If you think this issue is still relevant and applicable, you just have to post a comment and it will be unmarked.