Mac
If you are using PGV, you should have little to no need to run GEDCHECK after doing it once, before any editing with the program. You are very far beyond that stage and I'm at a loss to understand what you think you may learn. The program is designed to prevent entries that fail to comply.
Yes, GEDCHECK is very resource intensive, with large memory requirements. Also, unless you exported the current gedcom from your database before you ran GEDCHECK, you were running it on the original/old data. Hopefully, you are not using the SYNC to GEDCOM feature as it is a bit buggy (causing thousands of writes to disk that can easily become corrupted) and a drag on the system and wearing on your hard drive too with all the i/o.
Given the size of your GEDCOM, you'll need at lease 96mb, maybe more. -Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Stephen:
I occasionally run it to check that my sources are correct (sometimes I go too fast and enter "ste" didn't see the S# before moving on. Also I sometimes connect wrong members together and like to check I didn't leave fragments behind. It's a week past my third year of PGV :) My download gedcom zip was 758k with media, 3.7mb uncompressed.
Sounds like I'm running into this problem with everything I try to run in PGV.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mac
There are other vehicles to check your typing, autocomplete and SOUR list for SOUR, PLAC hierarchy for places, etc. GedCheck was not designed to overcome your data entry shortcomings. It will almost never find improperly attached persons unless there is a special crossover. However, do as you wish. YES, the larger your gedcom becomes, the more demanding of memory and other server resources all the programs will be. 64mb is really a bare minimum. Not sure what relevance there is on a compressed gedcom as you never work on a compressed file. -Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did some entries that gave me cause to want to do a gedcom check. Error received:
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 71 bytes) in /home/mydomain/tree/gedcheck.php on line 781
Mac
If you are using PGV, you should have little to no need to run GEDCHECK after doing it once, before any editing with the program. You are very far beyond that stage and I'm at a loss to understand what you think you may learn. The program is designed to prevent entries that fail to comply.
Yes, GEDCHECK is very resource intensive, with large memory requirements. Also, unless you exported the current gedcom from your database before you ran GEDCHECK, you were running it on the original/old data. Hopefully, you are not using the SYNC to GEDCOM feature as it is a bit buggy (causing thousands of writes to disk that can easily become corrupted) and a drag on the system and wearing on your hard drive too with all the i/o.
Given the size of your GEDCOM, you'll need at lease 96mb, maybe more.
-Stephen
Stephen:
I occasionally run it to check that my sources are correct (sometimes I go too fast and enter "ste" didn't see the S# before moving on. Also I sometimes connect wrong members together and like to check I didn't leave fragments behind. It's a week past my third year of PGV :) My download gedcom zip was 758k with media, 3.7mb uncompressed.
Sounds like I'm running into this problem with everything I try to run in PGV.
Mac
There are other vehicles to check your typing, autocomplete and SOUR list for SOUR, PLAC hierarchy for places, etc. GedCheck was not designed to overcome your data entry shortcomings. It will almost never find improperly attached persons unless there is a special crossover. However, do as you wish. YES, the larger your gedcom becomes, the more demanding of memory and other server resources all the programs will be. 64mb is really a bare minimum. Not sure what relevance there is on a compressed gedcom as you never work on a compressed file.
-Stephen