|
|
Customers Important Contributors FamilyTrees.GenoPro.com Translator GenoPro version: 3.1.0.1
Last Login: Sunday, March 21, 2021
Posts: 716,
Visits: 12,927
|
The first warning comes with an error message, the next one is the one below. If I cancel(right button) it crashes without the possibility to close other programs or to wait until memory level recovers by itself. Annoying!
|
|
|
Administrators Moderators Customers Gamma FamilyTrees.GenoPro.com Translator GenoPro version: 3.1.0.1
Last Login: Thursday, January 16, 2025
Posts: 4,887,
Visits: 22,775
|
Do you get this error message all the time, or after using GenoPro for several hours? Also, is it just saving to disk, or after doing an operation. Feel free to send me your latest file and I will investigate where the large memory allocation occurs and maybe I can reduce it. The old GenoPro was not designed to handle such a large number of object (you have more than 500,000 objects in your family tree).
The new GenoProX is much smarter about memory allocations and will be able to handle larger family trees, and on 64 bit, there will be no limit at all.
|
|
|
Customers Important Contributors FamilyTrees.GenoPro.com Translator GenoPro version: 3.1.0.1
Last Login: Sunday, March 21, 2021
Posts: 716,
Visits: 12,927
|
It changes after I make several changes or adjustments without saving in between. The memory level drops below 45%(app.). If it recovers to 47% or above(better50% or above) I have a good chance to save to HD. Will send the file to you.
|
|
|
Administrators Moderators Customers Gamma FamilyTrees.GenoPro.com Translator GenoPro version: 3.1.0.1
Last Login: Thursday, January 16, 2025
Posts: 4,887,
Visits: 22,775
|
I did a few modifications by adding and moving individuals and saved back your .gno file and on my machine. The peak memory was 462 MB. As long as the memory is below 2 GB (2048 MB), you should have no problem at all. You may push the peak memory to 3 GB, but it is a bit more risky.
GenoProX is designed completely differently and will be much faster. In your case, it will be at least 800 times faster, as each GenoMap is sandboxed for the undo/redo and a much smaller memory footprint when recording what was modified. Currently GenoPro 2016 visits every object when an operation is done to determine if the object was modified and serializes the entire object. The new undo/redo stack of GenoProX determines what are the possible objects which may be modified before attempting to compare them, and then serializes only what was modified. For instance, a typical move of an individual involves 5 objects: the individual, 2 pedigree links and the 2 families where the individual is connected so the line may stretch. If the individual was moved, then only its x,y position is serialized onto the undo stack, and perhaps the positions of the 2 families if stretched because the individual moved further than the previous family line(s). Since your family tree has 276498 objects, moving an individual is likely to be about 50,000 times faster with GenoProX, and perhaps a lot more since GenoProX uses dedicated virtual methods for undo/redo, bypassing all the serialization/unserialization overhead. I am sorry you are frequently running out of memory with GenoPro 2016. My recommendation is to keep the Task Manager open, and as soon as you see the peak memory reach 1 GB, close GenoPro and restart it. I can guarantee you the new GenoProX will not have this problem, as it will also be available in 64 bit, where the 4 GB memory limit will be something of the past.
Edited: Saturday, September 12, 2015 by
GenoProSupport
|
|
|
Customers Important Contributors FamilyTrees.GenoPro.com Translator GenoPro version: 3.1.0.1
Last Login: Sunday, March 21, 2021
Posts: 716,
Visits: 12,927
|
Thanks, will try my best to keep memory level under control.
|