with GPU turned off  I can start previewing multiple panoramas very easily. Slowly RAM fills up and when that is full the pagefile kicks in.  While scrolling at 150% things get slower and slower and more and more pagefile traffic happens. Tested it on a 16 GB machine but saw the same on a 64 GB one, just took a bit longer to fill the 64 GB and start the pagefile.

Closing all editors brings back the RAM usage to 9 GB from 16. Opening only two panoramas bring me back to 16 GB RAM used. closing these two bring me to 8 GB . Opening one to 13,5 GB again. Closing it to back to 8 GB again. Closing the programm bring me to 2 GB memory used.
Opening the programm again and loading all 6 panoramas but not in editor bring me to 3,43 GB used. This situation is the same as after I closed all 6 editors, the difference however is 5,4 GB, almost a GB for each panorama. Opening all panoramas in their own editor and then closing all of them again bring me to 3,93 GB RAM used to half a GB lost on just opening and closing 6 editors. Closing the programm totally bring me under 2 GB of RAM used again.

Seems like closing an editor does not remove all RAM that was used for that panorama. When working through a large number of panoramas this is a problem.
Also it seams that zooming and panning in the editor with preview is also waisting lots of memory.

Don't know what has changed between 3.0.0. and 3.0.3. regarding the memory used by the editor (doing preview) but I think I don't like it.

How is memory cleanup done while editors are open? After they have closed?  Is it garbagecollection methodoly in the sense that you need to give the programm some time/computer cycles to clean up after itself? Don't see that happening actually.

Last edited by HansKeesom (2013-01-21 23:39:01)

Hello,

I indeed reproduce a such behavior. Thanks for pointing that.
Issue 1742.

Regards,
Thomas

I am confused - could anyone clearly state to which exact versionS of APG does this apply to?

Thanks. I am still using 3.0.0  should I move to 3.0.1 or 3.0.2 or is it more reliable to use 3.0.0 for now?

Sorry Thomas,

but I am rather sure it was. I am previewing panoramas all the time and only noticed it at 3.0.3.   I used all version that existed. If I could I would gladly return to 3.0.2.

Thanks,

Just finished testing 3.0.1. and no experienced no memoryloss in that version. Hope to do 3.0.2. tomorrow.

in 3.05. the problem is still there. Have to close the programm totally to get all the memory back (32 GB) When loading all the groups again only 2 GB is used. After opening 4 editors I have used 3.5 GB.
Then I start doing previewing at different resolutions and see memory used growing again to 32 GB.  The programm will then cause the pagefile to be used a lot

If I then close all 4 editors does not solve the problem. The whole programm needs to be closed to be able to have normal use of memory again, starting at 2 GB again.

This is very annoying when working myself through a big multipanorama project.