Memory leak about chunky_png HOT 3 CLOSED

At the moment the library could not possibly do this, it loads each of those images into a stream, the issue is an unsigned int has a maximum size of a little over 2,000,000,000 bytes while all of your 875 256x256 total up to much more than that, and that’s assuming that ruby had no memory allocation limit (which it does), but long story short it is more data than ruby can store in one stream, thus the NoMemoryException occurs because ruby cannot write anymore information to temporary memory. Theoretically the library could be rewritten to write the output as it receives input information, but it would be a lot of work to rewrite such a large portion of the gem. Hope this helps ;-)

from chunky_png.

Try the https://github.com/libvips/ruby-vips

from chunky_png.

Closing this, as this is not a memory leak as explained in #144 (comment)

While it could be possible to have a more memory efficient implementation to help with tasks like this, it would require a significant rewrite of large parts of the codebase, which is not something I am planning to do any time soon.

from chunky_png.