Page 1 of 1

4.5 full version memory leak of album limitation??

PostPosted: Wed Dec 29, 2004 11:44 pm
by es
Hi,

Whilst going thru hundreds of pictures to preselect some for deletion i am creating an album that currently contains about 200 pics.
I am using the viewer to go thru the photo's and select them by hitting the '*' key. It starts out allright but after a while the memory usage goes thru the roof. I'm using a Pentium IV 2,4 GHz with 1GB of RAM. The systems start swapping like crazy and the task manager tells me over 1,5GB of the pagefile is in use. Closing cam2pc brings it back to about 200MB and i can restart cam2pc and select more pictures..... after a while.... you guessed it..... the same thing happens again.
So it doesn't look like a album size limitation, more like a memory leak...

Cheers
Elmar

PostPosted: Thu Dec 30, 2004 1:21 am
by Wally
I get the same results just using the full screen viewer. After going thru about 12 pictures quickly using the spacebar to advance the system memory usage goes way up until all virtual memory is used and the program crashes. The version before 4.5 did not have this problem.

Wally

Re: delete pics from album

PostPosted: Sat Jan 01, 2005 1:47 pm
by twin24
Hi es,

You said you created an album for pics to be deleted. How do you actually delete the pics? Can you do it from from the album menu, or do you have to trace the file back to its folder, and do it from there?

Thanks

PostPosted: Sat Jan 01, 2005 6:56 pm
by aeon
I can confirm there is a bad memory problem with Cam2PC 4.5.0 when viewing images full screen and paging quickly through them.

I have tested this on a folder of 1.5mb JPEGS whilst monitoring memory by performing the following actions
a) running cam2pc
b) paging quickly through 25 full-screen images
c) waiting for cam2pc to 'catch up' and display the last image selected
d) paging slowly through 10 further images
e) paging quickly through a further 25 images

At the outset of the test there was 280mb RAM used of 1Gb and 285mb in the paging file. Both figures rise rapidly if Cam2PC cannot 'keep up' with new images being requested.

When paging slowly through images allowing time for each to have fully displayed before moving on as during the middle section of the above test there is no noticable rise in memory used.

By the end of the above test RAM usage rises to my full 1Gb and the paging file likewise goes to 1.05Gb

I have repeated this test 3 times with consistent results. A graphical monitoring utility watching RAM shows it as follows with the 'plateau' part way up being the period I moved slowly through 10 images whilst to either side I moved quickly:

Image

After quitting Cam2PC memory is recovered.

PostPosted: Sat Jan 01, 2005 8:19 pm
by agent007
There definately seems to be a problem with the memory leak....I was watching the taskmanager and cam2pc memory usage went well over 100MB!!

Is nabocorp planning to fix this with a 4.5.1?

PS: The issue with the directory tree I had sometime back has been resolved with 4.5. Good work nabo!!

PostPosted: Sun Jan 02, 2005 9:34 pm
by nabocorp
Of course I will look into this and I'll keep you updated in this thread.

Regards,
nabocorp

PostPosted: Mon Jan 03, 2005 10:08 pm
by Jan Paul
Hi,

I am looking at the same problem here.

Memory used before opening Cam2PC: 226Mb.
Memory used after opening Cam2PC: 244Mb.
Memory used after browsing quickly (fullscreen) through about 10 images (1mb per piece): 534Mb.
Memory used after going to another directory and browsing quickly through about 100 images (1mb per piece): 1,2 Gb! System is slowed significantly due to memory swapping (I have 1Gb RAM).
Memory used after closing Cam2PC: 225Mb.

Regards,
Jan Paul

PostPosted: Tue Jan 04, 2005 9:02 am
by nabocorp
Hello,

this has been fixed in upcoming 4.5.1. The fix has been confirmed by aeon and his wonderful graphs :)

Regards,
nabocorp

PostPosted: Tue Jan 04, 2005 9:05 pm
by agent007
Glad to hear that!! Btw, the new layout looks very cool!!

PostPosted: Tue Jan 04, 2005 10:15 pm
by aeon
Indeed thanks to Nabocorps speedy update the memory problem now seems to be resolved. Running the same test as before shows a pretty much flat memory usage. (Minor fluctuation is normal when there is any computer activity).

Image

PostPosted: Tue Jan 04, 2005 10:37 pm
by nabocorp
Hello,

4.5.1 is released and should fix the bug. Get it!

Regards,
nabocorp

PostPosted: Wed Jan 05, 2005 10:58 am
by es
Great news!