Open Kroppeb opened 1 year ago
It seems I should call tiff.close()
, that seems to reduce the memory usage quite a bit. It seems there are still buffers being retained with the following gc path. Not quite sure yet where these are coming from.
has same issue
I have the following code:
The created URL's get revoked afterwards, yet there still seems to be a memory leak of some sorts. It also seem that once the memory leak hits a critical point, the library fails to read the data properly, and each subsequent image passed through causes an error. Yet those still keep increasing the memory footprint of the application.
I'm running this in FireFox btw, idk if that matters