Open fullben opened 4 months ago
Thank you! I'll see what I can do
Same for portable version
I've also seen this happenning. When I work a lot with GEDKeeper, my RAM starts slowly filling up and only empties when I close/restart GEDKeeper. After restarting and reopening the gedcom file, it doesn't use as much memory as before closing.
Was actually planning on reporting this myself soon
I'm not familiar with C# so idk if it's a thing, but in C++, whenever I create/allocate memory using type* x = new X
syntax, I have to manually release that memory using delete x
. Maybe that's the issue here? In last commit there are few examples of using new string[N]
or new List
, but they are never delete
d... Again, not familiar with C#, just trying to help a bit
Managed objects (string, List, etc) are freed automatically by the garbage collector when they go out of scope
There is a deeper problem, it may or may not be in my code, but definitely somewhere at the junction with the Eto.Forms framework and between it and WPF. The profiler detects severe memory loss in a number of areas, but cannot determine the exact location.
I keep looking. I won't close this issue for now
Environment
.ged
file, no external media, only people records, families...Observed Behavior
I have a nearly blank
.ged
file that I start out with. In the primary people tab, I start adding new people records. These records usually contain no information besides the persons' names, birth/death date and location, marriage information... I have not added any media or image data to the file.Every time I complete the input for a person's data in the popup and return to the main window, the main window will freeze. This behavior is observable even after having modified only a small number of records. The duration of the freeze increases over time and seems to be related to the number of modifications made in the popup windows. Memory usage also increases significantly over time.
Restarting the application usually "fixes" the issue in the sense that a few modifications work with little to no noticeable freezes before the freezes become noticeable again.
The following table gives a rough idea of the behavior I'm observing.
If left idle, the application's memory usage remains constant.
On a previous run, I created a new file, added about 30-50 people and then had the app freeze (at the point in the workflow described above), before it finally crashed on me. During that run, the following error output appeared in the application log:
Disclaimer
I'm new to the field of genealogy, maybe I'm doing something wrong when entering my data.