Re: [Ginp-developers] BUG :-(

[Doug C. <do...@cu...>]

I could not reproduce this error locally only on my live webserver 
(which  has been up 495 days).  The tomcat server has been running a few 
months and so I stopped and started it.  The problem was fixed once it 
started.   Therefore I think that this is not really a ginp problem.

The resizing of images is a big computing tasks but it is needed to make 
the application preform well (or at all) on low bandwidth connections.  
The resize is fast on a server and only one image is resized at a time.  
The thumbnails come from the disk and are made once by a background 
thread.  Therefore a test gallery of 1000 pic will not make a big 
difference.  I think that the culnane.navidat.com webserver just got in 
a bad state.  If it happens again I will try to increase the memory 
tomcat used at start up.

If you think I have missed something serious then let me know.

All the best,

Doug

Justin wrote:

> Doug Culnane wrote:
>
>>
>> It is still there:
>> http://culnane.navidat.com/dc/ginppic?path=%2FBoats+and+Builds%2F&name=DSC07655.JPG&height=647 
>>
>>
>>
>
> Doug,
>
>     I think you're running out of memory because of the height 
> parameter. If you remove it it runs fine.  Just click on the link 
> below to see what I mean.
>
> http://culnane.navidat.com/dc/ginppic?path=%2FBoats+and+Builds%2F&name=DSC07655.JPG 
>
>
> I looked at the code and when the height is on you have to take a 500k 
> compressed image, decompress it and make another copy of it 
> transformed.     This is a very memory intensive operation.  When you 
> don't put the height parameter on it you can just stream it off of the 
> disk a byte at a time and this works fine.
>
> Regards,
>
>     Justin
>
>
>


-- 
Doug Culnane
do...@cu...
www.culnane.net