Thread

Hi, I have a site running EE 1.7.0 hosted at EngineHosting. Everything about it runs perfectly but when I try to register a new member I get an out of memory error in the CP:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 71 bytes) in /www/[enginehosting account]/public_html/[system folder]/core/core.validate.php on line 489

I’ve tried with extensions disabled and with my .htaccess file blanked out and the error sticks. I’ve taken it up with EngineHosting and they have bounced me to here. They have always been excellent in the past and I find it strange that it is possible to run out of PHP memory by performing such mundane task in the control panel.

Please help soonest as I need to register a bunch of new content administrators to get the site up and running by the project deadline.

Of course let me know if you need further info or login details for the site.

Thanks

Hi Luke,

Can you tell us what add-ons you are running?

Hi John, it turned out it wasn’t related to addons, at least not directly. The problem was the standard 23 meg EE1 dictionary file which the member registration process checks when registering a new member or changing passwords.

I managed to sort this by looking through the core file throwing the error and finding the call to open the dictionary file, which I then removed from the site preferences.

Not ideal that a standard process should cause my EH account to run out of memory though (64 meg limit).

Luke,

There is no standard dictionary file included with a base install of EE1.x not a 23MB one at least 😊
Was this a file you added yourself?

Do you have a file name added under Name of Dictionary File

CP Home ›  Admin ›  System Preferences ›  Security and Session Preferences

Oh sorry, 2.38 megs not 23. Pretty sure it’s the standard file - not added by me but by the previous webmaster. The effort required to check every word in the dictionary seems to be what caused the server to run out of memory.

Luke the base install of EE is under 2MB at the moment so likely a file added by your previous webmaster which is fine but as you found out it can be memory intensive.

You seem to be up and running again though which is what matters. Removing the reference to the dictionary file where I mentioned should have done it for you.

I’ll close this thread out for you if you wish?

Thanks for your help John, yes all is well again, go ahead and close the thread.

Glad you found the culprit, Luke. Thanks.