3 ms·
Yep, could someone take this over? And, also fix all the memory leaks while you're at it, thanks! (http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=rmagi
by aditya 16y ago
Yep, could someone take this over? And, also fix all the memory leaks while you're at it, thanks! (http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=rmagick+leak http://www.google.com/search?sourceid=chrome&ie=UTF-8...)
- pilif 16y agoWhat kind of an attitude is this? If you care so much about the memory leaks, fix them yourself. It's open source after all. Requesting bugs fixed this way is bad in a normal situation, but doing so as an answer to a call for help to keep the project moving forward is disgraceful.
- Argorak 16y agoMight I suggest that you also read the explanations in the first result? http://stackoverflow.com/questions/958681/how-to-deal-with-memory-leaks-in-rmagick-in-ruby/959473#959473
- mmcdan 16y agoSuccessful use of rmagick also requires that you explicitly call the ".destroy!" method on all images(including intermediary ones) to ensure that memory is freed up. Looking at Ruby's Object space shows that this method successfully marks the images for deletion. This eliminated the memory leaks for me. You may have to also call GC.start after ".destroy!" if you want the objects cleaned up as quickly as possible. See: http://rubyforge.org/forum/forum.php?thread_id=1374&forum_id=1618 http://rubyforge.org/forum/forum.php?thread_id=1374&foru...