ImageScience is a clean and happy Ruby library that generates
thumbnails -- and kicks the living crap out of RMagick. Oh, and it
doesn't leak memory like a sieve. For more information including build steps, see http://seattlerb.rubyforge.org/
Changes:
## 1.1.3 / 2007-05-30
* 2 minor enhancements:
聽聽聽* Added quick_thumb as an example to look at.
聽聽聽* Error handler doesn't raise by default. Raises if $DEBUG==true.
For what it's worth, I run rmagick in a (lightly-used) production
service on a win32 box and have had no problems, memory usage appears
stable over time. I had actually considered image_science as an
alternative, but given the lack of an image_science gem that doesn't
depend on having a c compiler on the box (a relative rarety in the win32
world, sadly), it's not an option for me.
- donald
路路路
On May 30, 2007, at 3:38 PM, Ryan Davis wrote:
> and kicks the living crap out of RMagick. Oh, and it doesn't leak
> memory like a sieve.
If you know of a leak that isn't addressed by that tip, I'd love an opportunity to fix it. Would you mind sending me a script that
reproduces the leak? I need a script with no extra gems or libraries, just Ruby and RMagick. No Rails, attachment_fu, file_column, gruff,
scruffy, or whatever. Let me know what O/S you're on, what version of RMagick and ImageMagick/GraphicsMagick, and what version of Ruby. You can send it directly to me, post it here, or open a bug track on RubyForge.
By the way, since I originally posted that request on the 17th I've had no new bug reports, so please, send 'em in.
More FUD! How many times I've heard this crap I have no idea... We've been shipping inline with inline_package for over 2 years now. How long do you have to propagate this?
路路路
On May 30, 2007, at 17:13 , Ball, Donald A Jr (Library) wrote:
I had actually considered image_science as an
alternative, but given the lack of an image_science gem that doesn't
depend on having a c compiler on the box (a relative rarety in the win32
world, sadly), it's not an option for me.
Well, I was thinking it might be worth it to submit bug reports to the tracker so he could fix them. I see from your article that you've had trouble with that in the past though. Fair enough.
James Edward Gray II
路路路
On May 30, 2007, at 4:15 PM, Ryan Davis wrote:
On May 30, 2007, at 16:58 , James Edward Gray II wrote:
On May 30, 2007, at 3:38 PM, Ryan Davis wrote:
and kicks the living crap out of RMagick. Oh, and it
doesn't leak memory like a sieve.
Ryan, glad to see you've constructively channeled your frustrations with
RMagic.
Two wrongs don't make a right but two developers with differing opinions
make two very useful pieces of software.
Keep up the good work guys
路路路
On 5/30/07, Tim Hunter <TimHunter@nc.rr.com> wrote:
James Edward Gray II wrote:
> On May 30, 2007, at 3:38 PM, Ryan Davis wrote:
>
>> and kicks the living crap out of RMagick. Oh, and it
>> doesn't leak memory like a sieve.
>
> The creator of this library disagrees, just FYI:
>
> http://groups.google.com/group/comp.lang.ruby/msg/a61984b06e70acea
>
> James Edward Gray II
>
Thanks for reposting my earlier request, James. I'll repeat it here for
emphasis:
If you know of a leak that isn't addressed by that tip, I'd love an
opportunity to fix it. Would you mind sending me a script that
reproduces the leak? I need a script with no extra gems or libraries,
just Ruby and RMagick. No Rails, attachment_fu, file_column, gruff,
scruffy, or whatever. Let me know what O/S you're on, what version of
RMagick and ImageMagick/GraphicsMagick, and what version of Ruby. You
can send it directly to me, post it here, or open a bug track on
RubyForge.
By the way, since I originally posted that request on the 17th I've had
no new bug reports, so please, send 'em in.
Apologies for the misinformation. All I know is that on my win32 box, if
I gem install image_science and all its dependencies,
路路路
On May 30, 2007, at 17:13 , Ball, Donald A Jr (Library) wrote:
> I had actually considered image_science as an alternative,
but given
> the lack of an image_science gem that doesn't depend on having a c
> compiler on the box (a relative rarety in the
> win32
> world, sadly), it's not an option for me.
More FUD! How many times I've heard this crap I have no
idea... We've been shipping inline with inline_package for
over 2 years now. How long do you have to propagate this?
Have you guys had problems deploying Rails apps with ImageScience and
Mongrel? I tend to get strange errors about RubyInline not having access to
the home directory. Similar to the problem described here ( http://www.ruby-forum.com/topic/109129\), but with this fix not quite being
100% effective.
路路路
On 5/31/07, Ball, Donald A Jr (Library) <donald.ball@nashville.gov> wrote:
> On May 30, 2007, at 17:13 , Ball, Donald A Jr (Library) wrote:
>
> > I had actually considered image_science as an alternative,
> but given
> > the lack of an image_science gem that doesn't depend on having a c
> > compiler on the box (a relative rarety in the
> > win32
> > world, sadly), it's not an option for me.
>
> More FUD! How many times I've heard this crap I have no
> idea... We've been shipping inline with inline_package for
> over 2 years now. How long do you have to propagate this?
Apologies for the misinformation. All I know is that on my win32 box, if
I gem install image_science and all its dependencies,
That's the first I've heard of for mongrel. I just dealt with something similar on apache and blogged my fix for that. I rejected a bug yesterday for a similar sounding Locomotive bug but the reporter couldn't and wouldn't provide a reproducible test case (besides an entire rails app + downloading locomotive (46m) etc etc). No clue if that is related or not as he just couldn't get any clarity on the issue.
So, try my blog. Let me know if that works for you.
P.S. Setting HOME is not the answer. Set INLINEDIR instead.
路路路
On Jun 1, 2007, at 00:30 , James Herdman wrote:
Have you guys had problems deploying Rails apps with ImageScience and
Mongrel? I tend to get strange errors about RubyInline not having access to
the home directory. Similar to the problem described here ( http://www.ruby-forum.com/topic/109129\), but with this fix not quite being
100% effective.
Could I get some help setting up image_science in my win32 environment?
I've never worked with RubyInline and I think that's where I'm getting
stuck. I have both Visual Studio 2003 and 2005 installed. So far, I've
gotten:
For more information including build steps, see http://seattlerb.rubyforge.org/