Actually, on further testing it does look like it the 'self.pictures
<< @photo ' that eats up all the memory. Yes, each image is very
large. So time to look for a new solution. Shame.

On Aug 13, 10:32 pm, kevin  evans <kwev...@[...].com>  wrote:
>  Thanks for the replies.
> 
>  Bryan, Soory I'm a bit of a ruby newbie (still!!!), do you mean use
>  some form of syntax for the Find that returns all images as an array,
>  for processing?
> 
>  also @photo = nil (is that what you mean?
> 
>  On Aug 13, 10:17 pm, Bryan Duxbury <rails-mailing-l...@[...].net>
>  wrote:
> 
>  > Have you tried just doing the Find::find stuff without a body and seeing
>  > if that accumulates a ton of memory? If it doesn't, then you might want
>  > to explicitly nil out the @photo after it's been saved. Likewise, it
>  > look like you never close all the Files you are opening. You might want
>  > to watch out for that.
> 
>  > Finally, how big are these jpgs? Are they super-compressed, so that they
>  > actually do take up a ton of memory when loaded?
>  > --
>  > Posted viahttp://www.ruby-forum.com/.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Ta
lk" group.
To post to this group, send email to rubyonrails-talk@[...].com
To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe@[...].com
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---