Memory Exhausted - no suggestions yet helpful
Brought to you by:
canajun2eh,
yalnifj
Menu
▾
▴
I have newest script Dec 2009. 64 MB memory on my server php 5, MySQL 5+, and still get error that memory exhausted even when my gedcome is only 4 MB in size. I HAD a gedom that was 35 MB that ran on an earlier version of phpgedview so why is it not possible to run on this newer script. Considering going back to the older script as this new script doesn't seem to support bigger files/imports. Is there a way to convert backwards without having to reinstall the whole program?…or a way to fix the problem. The suggestions on writing an .htaccess to increase memory didn't help as after I put the file in the phpgedview directory, it returned an error on my site.
64MB should be OK.
Are you *really* sure you have 64MB. Just because you request it, doesn't mean you have it. What does phpinfo show?
nope….it says 64 MB right on the phpinfo.php page on my server http://www.npcanada.ca/phpinfo.php
memory_limit 64M 64M
yet i get this error if a file is any larger than 3.8 MB
Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 4608001 bytes) in /home/donna1/public_html/phpgedview/uploadgedcom.php on line 958
i think i remember doing something with the session path on the older version and it helped import larger files…but i can't remmember what i did on the previous version. I'm going to try and set session save path to ./index/ and see if that works because right now, my server has no session save path.
My gedcom is 15.1MB. With a memory limit of 48MB, I can import it OK. (but it fails if I reduce the limit to 32M). So, a 64MB limit really should be fine.
What language are you using? It can help to switch to english, as the texts are generally shorter than in other languages, and hence use less memory.
Hello npcanada -
While many of us would "kill" for the 64MB allocation you have, it is possible that your MySQL version is a bit lower than that required for versions of PGV after 4.2 This is from the Install Wiki - http://wiki.phpgedview.net/en/index.php?title=Installation_Guide_v4.2.x#Requirements - REQUIREMENTS: Your web server needs to be running PHP version 5.2 or greater to generate dynamic HTML pages and use all of PhpGedView 4.2.x functions.
Perhaps this could be the source of your delays, but unfortunately I have no suggestions on a remedy. I provide this observation for others to possibly assist you. Good Luck and Welcome to PGV !
RL
Hello npcanada -
Oops. I meant to imply that perhaps your Databases were not set up as MySQL 5.x-type. On my webhost, I am given the option to create version 4 or version 5 compatible datbase. Sorry for the confusion in the previous post.
RL
Yes, it seems to fit all of those criteria/requirements and exceeds them. My hosting company assured me that it should work…and it has worked …up until I installed the newest Dec 2009 version. I'm going to go back to the 4.16/4.17 version. Less headaches.
wow…now i have asked my host to increase to 128 M memory, max upload 50 M, max file size 55 M, max execution 180 seconds, and I can't get ANY version to install a file larger than 3.8 MB. (even the old version that used to work on my server). this is frustrating…they even went as far as installing pgsql for me to try an upload it into a different database…worked for 10 MB but same error at my 27 MB file….fatal error: memory exhausted
SOLVED - Instead of running the php time limit to '0' which is what i was using before, I set the time limit to 60….and said 'press continue' automatically and it kept running for 60 seconds about 16 times and then it was complete. I never even thought about setting it to 60 seconds as I thought it would time out at 60 and needed A LOT more time than that…so I set it to '0" as that is what I know I had set for my previous site.
Donna
The import procedure counsels you that, should your import fail, you should reduce the time for time-out and try again, being sure to use the auto-continue function. This procedure is designed to defeat a PHP timeout by stopping the import procedure prior to exhausting memory and time constraints and then restarting it for another time period, again and again, as often as is required by the import script. This time can vary widely due to server memory, server speed, connection speed and more.
However, setting a script to ZERO has never been part of the import process.
-Stephen
Yes, I did read the instructions about setting the time limit down if the continue button doesn't appear and the import fails but from my last install this did not work for me. The only way it worked PREVIOUSLY for me was to set the time limit to '0' so I naturally assumed it would only work that way again for a fresh install…so I never even tried the default. I did try setting the time limit to something like 300 seconds thinking that is the time I needed to import the gedcom…difficult to understand how setting the time LOWER will allow a larger file to import whereas setting the time limit HIGHER will cause it to time out or exhaust the memory.
but of course…it does make sense now that each 60 seconds empties the cache or resets the memory like you said…but setting it to '0' causes the memory to just keep rising until it is completely used up rather than refreshed every 60 seconds.
I'm having the same problem. I've lowered the time limit progressively until I'm down to 10 seconds and it STILL gives me the same fatal error message! I've had my hosting company increase my limit, lowered the time, and still no luck importing my first GEDCOM. Have I missed something?
Honey
What is your memory limit? Have you changed it in PGV as well as in the php.ini? What does you phpinfo say?
How large is your gedcom? (mb or INDI's) From whence did you derive this GEDCOM (program export, relative, etc)? Are you sure it is properly configured? (head and trailer?)
You can zip it up and send it to me for import into my offline PGV test setup and I can see if I can note any issues. I'll also run it through geditcom for possible errors.
mailto:gedcom-at-MyArnolds-dot-com
Stephen
Hi Stephen :)
My memory limit has been increased to 64mb, so that shouldn't be the problem. I can't find the phpinfo file, can you give me some directions on finding that please? I've never used a program like this, so I'm definitely wet behind the ears! ;) My GEDCOM is 2.61mb and it was exported from Family Tree Maker on my own computer. When you ask if it's properly configured, I'm not exactly sure what you mean, but I did export it into GEDCOM format from FTW. I'll fire it off in an email to you after I post this, and thanks for your help, I appreciate it immensely!! :D
Robyn.
Hey Robyn
You've answered some, but still not all of the questions needed to supply help. Remaining:
phpinfo file is accessible from your ADMIN page, http://your-pgv-site.xxx/pgvinfo.php?action=phpinfo
What memory have you assigned from the 64mb to PGV in the configuration?
and select Advanced Settings > Memory limit
Your gedcom is certainly small enough to be imported into PGV quite readily with 64mb of memory, so I suspect either you do not have the 64mb available from PHP or you do not have it fully assigned to PGV operations. I'll await your additional replies on and or offline.
Stephen
Hi Stephen :)
I finally got to the memory limit after some blonde moments! I've changed the limit to 64mb, will try importing again and see how I go. Hopefully I'll be back with some good news! :D
Robyn.
I'm back, hopefully for the last time! lol I had to drop the time limit down to 5 seconds, and it went through exceptionally fast after all that! Thanks so much for your help Stephen!!! :D
Robyn.
robyn
I'm quite surprised at the 5 second limit, as it worked just fine on my system with 30 seconds and with only 32mb assigned. You have mentioned that this is a hosted site, so perhaps the connection speed or server 'horse-power' may not be up-to-snuff.
Glad you were able to resolve this problem and thanks for reporting back.
Stephen
Robyn
Part of the import issue was the ANSI formatting of your gedcom file, rather than utf-8. The conversion of these mismatched files is a much larger strain on the server resources. This would be the primary issue leading to the very low 5-sec setting necessary to successfully import your file into PGV on a hosted platform.
Stephen
Hi Stephen :)
I noticed this myself, so I went into FTW to see if there was an option of how to export, and there wasn't. I only had the choice of "GEDCOM 5.5 (Standard)" or "GEDCOM for FTM 16". Version 16 is pretty old, so I chose the 5.5 option. I'll have to look into this a bit further, this is a new version that I haven't had time to sit and play with much. At least it's working now, thanks for your help!! :D
Robyn.