[<<][webdev][>>][..]
Wed Dec 19 20:39:40 EST 2018

Performance

The previous approach works, but it seems to create quite large
browser resident size.  Some collection is going on but over time it
leaks.

Maybe use a canvas instead?

https://stackoverflow.com/questions/9913765/rapidly-updating-image-with-data-uri-causes-caching-memory-leak

It will still need the url converter..

Anyways, one thing to do is to turn off the stream when not visible:

https://developer.mozilla.org/en-US/docs/Web/API/Page_Visibility_API



EDIT: It seems to no longer leak with the release call.



[Reply][About]
[<<][webdev][>>][..]