Fatal error: Allowed memory size of 402653184

I just upgraded to v4.2.3 basic from 4.2.0 and am getting the following error:

Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 10995125 bytes) in /home/httpd/www/nwcascades.com/gedcom/uploadgedcom.php on line 958

My GED file is 33958.66Kb

What's the fix here… or should I go back to the old version?

Jack

Hi Jack. Absolutely no need to reverty back to old version, and you may well find the same problem anyway.

The answer is pretty much the same as when you asked the similar question when you upgraded to ver 4.2:

> Don't try to import the GEDCOM in one
> fell-swoop. Use the auto-continue
> option and set the time for about
> 20-30 seconds. You shouldn't need more
> than 128mb.
>
> As the instructions say, should the
> import fail, start again with a LOWER
> setting.

Actually the old version worked on a daily basis. There are apx. 130K induviduals in the GEDCOM and growing.

In 4.2.0 the import progress bar incremented properly with a timeout of 15 sec. and a memory setting on 384Mb.

In 4.2.3 the import progress bar never moves with these settings. If I set memory to 512Mb and timeout to 2500 sec. it makes it to about 91% of completion.

What exactly should be done here?

Jack

> If I set memory to 512Mb and timeout
> to 2500 sec.

Two problems with that statement Jack:

1 - When you say "set memory to 512Mb", are you doing it in BOTH PGV's config AND your php.ini file? PHP can only use the lower of these two, so setting PGV to anything higher than set in your php.ini file is futile.

2 - Setting timeout to 2500 sec is going the wrong way. to trigger the auto-continue (or even manual 'continue') option you need to LOWER the timeout. This ensures PGV can stop in a controlled fashion before the server crashes, and so allow continuation from a virtual restart.

4.2.3 has a lot of improvements over 4.2.0, requiring a lot of DB changes. this will be why on this first re-import it is taking a long time.

You might also check your DB collation settings, to ensure they are consistent across ALL tables, and ALL FIELDS within each table. This can also effect DB operations considerably. This patch might help there:

    https://sourceforge.net/tracker/index.php?func=detail&aid=2318005&group_id=55456&atid=477081

Jack  
I have 1/2 that many (about 70k INDI's), but my GEDCOM is 40mb. A very fast server with tons of memory, but a first import - even with the DB optimized - can take about 20 minutes or more and that with the auto-continue setting at 15 seconds. 
Hope this helps, Stephen

It finally completed the import. This as previous imports were replacing previous databases. I reset the Mem Limit to 128, and timeout to 20 Sec. and it completed successufully.

It took abt 40 min.

Following my previous comment, the "Most Common Surnames" display has become quite large. Where is the threshold number of families stored?

The Common Surnames threshold is in the GEDCOM configuration.  Look at the Display and Layout group, Common Surnames section.

Changes you make here won't be reflected in the list until you do another import.  There might be other conditions under which a new list is produced, but I don't know what triggers this.  It's been a very long time since I looked at this code.

You can manually edit the GEDCOM file list in file "index/gedcoms.php".  There is a Comon Surnames list in this file, and you can change the list if needed.  You should proceed with caution if you choose to manually edit this file.  Be sure to keep a backup so that if things fall apart you can revert to the original file easily.

> You can manually edit the GEDCOM file
> list in file "index/gedcoms.php".
> There is a Comon Surnames list in this
> file, and you can change the list if
> needed.

That used to be the case, but the performance of this query has been significantly improved, and we no longer cache this value in gedcoms.php.  It is always re-calculated as needed.