WebRTC is very complicated for photos about jscanify HOT 5 CLOSED

OK, so you are able to get high res images, but are experiencing memory leaks?

from jscanify.

Interesting. From what I gather, you are having trouble getting high resolution images through WebRTC?
Could you share the code you're using? Might be able to help from there.

from jscanify.

It's just to have the getUserMedia with a constraints of 1920 or higher...
OpenCV Mat has a known bug with garbage collector (opencv/opencv#15060) and when you use video or high resolution photo is too heavy for Javascript.
I'm trying to use to capture more than 1 document, and if the "session" lasts more than 3/4 minutes, it finally crashes resulting in a memory fault.
I've tried to "delete" everything possible, but it's something very "deep" in OpenCV.

from jscanify.

Hmmmm, ok. If it's a problem on OpenCV's side then there's not much I can do, but I'll take a look to see whether there could be some fault on my side exacerbating this problem.
I wonder whether you could simply set a timer on the camera? E.g., after 45 seconds automatically close the stream due to inactivity.

from jscanify.

I already tested it.
The problem is that OpenCV does not "clean" well.
The problem is not from the streaming that "overloads" the memory, but from each time you call OpenCV to do the calculations.
That is, it is as if you have a "maximum number of seconds where OpenCV works".
Even if you cut the streaming, it doesn't minimize the overall problem.
I'll keep thinking of something.

Of course, all this happens when you want to make a "long" and continuous use of OpenCV with resolutions beyond 800x600.

from jscanify.