On Sun, Jan 30, 2005 at 12:06:01AM +0000, Richard Lamont wrote:
> I started it again and looked at what was happening with top, and found 
> that digikam was reserving memory of the same order of magnitude as the 
> total size of the files downloaded. (After downloading about 130 
> pictures it had hogged about an extra 100 MB of RAM.) Closing the 
> camera window freed the memory.

I don't know if I would call this a memory leak as it does free the
memory after it has finished with it. A memory leak wouldn't retun the
allocated memory.

That said I can confirm the behaviour as I just uploaded over 100
pictures from a full 256Mb card and digikam ended up reserving over 250Mb of
main memory. That said my machine didn't thrash and was still responding
well.

Perhaps this is a design issue and as has been pointed out gphoto keeps
all photo's in memory as a matter of course.

Can you try switching off other Linux processes and see if you machine
still starts to thrash.  Then again if your machine is trying to swap
1Gb of photo's with only 512Mb then perhaps you should also 'invest' in
some disk swap space to make your memory footprint over the 1Gb.

Mark


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to