Hi, everyone! I have been recently hit by ImageMagick/Rmagick memory leak issues. I know I can lesson the problem by manually starting up GC each time I use Rmagick library but ImageMagick seems to use way too much memory nevertheless. (on shared hosting setup anyway) Is there a decent replacement for ImageMagick library? I used to think ImageMagick was quite efficient because its speed was order of magnitude faster than pure java image libraries. Is it really a resource hog, or is it just the way it is with image processing? (I normally use ImageMagick only for resizing/cropping images, nothing too fancy.) I will appreciate any comments or suggestions, thanks! best, daesan
Hi ! 2006/4/24, Dae San Hwang <daesan@gmail.com>:> Is there a decent replacement for ImageMagick library? I used to > think ImageMagick was quite efficient because its speed was order of > magnitude faster than pure java image libraries. Is it really a > resource hog, or is it just the way it is with image processing? (I > normally use ImageMagick only for resizing/cropping images, nothing > too fancy.)Look into MiniMagick: http://rubyforge.org/projects/mini-magick/ Hope that helps ! -- Fran?ois Beausoleil http://blog.teksol.info/
Thank you Francois for the reply. But MiniMagick also seems to be a ruby front-end for ImageMagick library, just like RMagick. cheers, daesan On Apr 25, 2006, at 4:06 AM, Francois Beausoleil wrote:> Look into MiniMagick: http://rubyforge.org/projects/mini-magick/Dae San Hwang daesan@gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060425/82c41394/attachment.html
Dae San Hwang wrote:> Thank you Francois for the reply. But MiniMagick also seems to be a > ruby front-end for ImageMagick library, just like RMagick. > > cheers, > daesan > > > On Apr 25, 2006, at 4:06 AM, Francois Beausoleil wrote: > >> Look into MiniMagick: http://rubyforge.org/projects/mini-magick/ > > Dae San Hwang > daesan@gmail.comWell what''s the cause of the memory leak? ImageMagick or RMagick? If it''s RMagick then maybe MiniMagick doesn''t suffer the same leak problems? I need to figure it out one way or another since I''ve put in a request with my hosting provider to install RMagick (on a shared account at that). So if there are any leak issues and such that may cause problems in my shared hosting environment I should probably get them to also take a look at mini magick. -- Posted via http://www.ruby-forum.com/.
The cause of the memory issues seems to be RMagick, unfortunately. I''ve had lots of such problems, but I''m reluctant to rewrite a big chunk of my code to use MiniMagick because it seems like a "hack." Not to put down MiniMagick, it''s just that I''m hoping RMagick might get fixed somehow. MiniMagick is just a kind of wrapper that calls ImageMagick under a separate process, is how I understand it. May be wrong.
I''ve installed RMagick using the GraphicsMagick library (instead of ImageMagick) and when using file_column to upload and resize images, i get serious memory problems too - after the upload, the RAM just fills up until i kill everything ruby... Steve The Barge wrote:> Dae San Hwang wrote: > >>Thank you Francois for the reply. But MiniMagick also seems to be a >>ruby front-end for ImageMagick library, just like RMagick. >> >>cheers, >>daesan >> >> >>On Apr 25, 2006, at 4:06 AM, Francois Beausoleil wrote: >> >> >>>Look into MiniMagick: http://rubyforge.org/projects/mini-magick/ >> >>Dae San Hwang >>daesan@gmail.com > > > Well what''s the cause of the memory leak? ImageMagick or RMagick? If > it''s RMagick then maybe MiniMagick doesn''t suffer the same leak > problems? I need to figure it out one way or another since I''ve put in > a request with my hosting provider to install RMagick (on a shared > account at that). > > So if there are any leak issues and such that may cause problems in my > shared hosting environment I should probably get them to also take a > look at mini magick. >
Whoa, there seems to be many others suffering from this problem! Read http://rubyforge.org/forum/forum.php? thread_id=1374&forum_id=1618 You can lesson the problem by manually calling GC.start best, daesan On Apr 26, 2006, at 5:09 AM, Raymond Brigleb wrote:> The cause of the memory issues seems to be RMagick, unfortunately. > I''ve had lots of such problems, but I''m reluctant to rewrite a big > chunk of my code to use MiniMagick because it seems like a "hack." Not > to put down MiniMagick, it''s just that I''m hoping RMagick might get > fixed somehow. MiniMagick is just a kind of wrapper that calls > ImageMagick under a separate process, is how I understand it. May be > wrong. > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/railsDae San Hwang daesan@gmail.com