-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fatal error: Allowed memory size exhausted on SilverStripe 3.1.1 #27
Comments
Same here with SS3.1, PHP 5.3.6, and MAMP 2.1.1. Thing that has changed on my side is upgrade to Maverick OS X 10.9 ? |
I think this has more to do with the built-in version of PHP. When you run SilverSmith, you're not using the version of PHP that MAMP runs on. The version that comes built into Mavericks is v5.4.17. That might have something to do with it. |
Thanks, so I'll have to look into the php.ini of the "Mavericks" php version... |
Have been spending some time to add and configure php.ini, but... to no avail... sudo cp /etc/php.ini.default /etc/php.ini memory_limit = 256M |
Yes, I had to ensure SilverSmith was using MAMP, otherwise I got the same errors. For me it was export PATH=/Applications/MAMP/bin/php/php5.3.6/bin:$PATH |
Just tested using a fresh install of SilverStripe 3.1.1 with Composer and got a "Allowed memory size" error when I run just about any SilverSmith command. I'm using MAMP Pro 2.2 on OS X Mavericks with PHP set to version 5.3.27. Just to be sure, I tested it with SilverStripe v3.0.8 and didn't get any error so...me thinks it's something in version 3.1.1 that's messing with it. Here's the full error:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 130968 bytes) in ..../framework/dev/Deprecation.php on line 82
The text was updated successfully, but these errors were encountered: