memory leak? about jsmpeg HOT 3 CLOSED

@indus i know you asked this a long time ago but for anyone stumbling on this now. You can use JSMPEG with socket.io! See my gist here https://gist.github.com/moeiscool/e2a584cca6f4e3f1691a96b6c56856f9

I modified the library to work as a pipe. https://github.com/ShinobiCCTV/jsmpeg-pipe So we can write data as we are emitted it from socket.io

from jsmpeg.

Narf. Finding the cause for such memory leaks is notoriously difficult. I'll look into it. However, it doesn't seem to be that bad - judging from your screenshot, it only rises about ~2mb in 10minutes :)

To solve the other problem, you could close() the WebSocket (and maybe throw the jsmpeg instance away altogether) when the page is hidden and reconnect/recreate when it becomes visible again. Support for the page visibility API is quite good, but it's still a bit of a pain to use with all the vendor prefixes currently.

from jsmpeg.

using visibility API to kill the stream instance sounds ok. Thanks.

Just another short question: I already have a socket.io server running in my project. It spreads some realtime GPS-positions to a handfull clients. Do you think its better to integrate the video-streaming into the existing "socket.io"-server, and avoid a second websocket-server?... or to run them separately side-by-side?

from jsmpeg.