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

More memory #427

Closed
simonwheatley opened this Issue Aug 26, 2014 · 9 comments

Comments

Projects
None yet
6 participants
@simonwheatley
Contributor

simonwheatley commented Aug 26, 2014

Is anyone else running into issues with the VM not having enough memory? I'm seeing this with Composer:

PHP Fatal error:  Uncaught exception 'ErrorException' with message 'proc_open(): fork failed - Cannot allocate memory' in phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:981
Stack trace:
#0 [internal function]: Composer\Util\ErrorHandler::handle(2, 'proc_open(): fo...', 'phar:///usr/loc...', 981, Array)
#1 phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php(981): proc_open('stty -a | grep ...', Array, NULL, NULL, NULL, Array)
#2 phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php(799): Symfony\Component\Console\Application->getSttyColumns()
#3 phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php(760): Symfony\Component\Console\Application->getTerminalDimensions()
#4 phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php(690): Symfony\Component\Console\Application->getTerminalWidth()
#5 phar:///usr/local/bin/com in phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php on line 981

Fatal error: Uncaught exception 'ErrorException' with message 'proc_open(): fork failed - Cannot allocate memory' in phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php:981
Stack trace:
#0 [internal function]: Composer\Util\ErrorHandler::handle(2, 'proc_open(): fo...', 'phar:///usr/loc...', 981, Array)
#1 phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php(981): proc_open('stty -a | grep ...', Array, NULL, NULL, NULL, Array)
#2 phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php(799): Symfony\Component\Console\Application->getSttyColumns()
#3 phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php(760): Symfony\Component\Console\Application->getTerminalDimensions()
#4 phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php(690): Symfony\Component\Console\Application->getTerminalWidth()
#5 phar:///usr/local/bin/com in phar:///usr/local/bin/composer/vendor/symfony/console/Symfony/Component/Console/Application.php on line 981

See: composer/composer#945 (comment)

@westonruter

This comment has been minimized.

Member

westonruter commented Aug 26, 2014

I had problems with memory running over as well. I fixed it by dropping in a Customfile:

config.vm.provider :virtualbox do |v|
  v.customize ["modifyvm", :id, "--memory", 1024]
end
@simonwheatley

This comment has been minimized.

Contributor

simonwheatley commented Aug 26, 2014

I had not realised you could override parameters like that. 😄

@simonwheatley

This comment has been minimized.

@jeremyfelt

This comment has been minimized.

Member

jeremyfelt commented Aug 26, 2014

Is this worth bumping the memory limit by default?

@jeremyfelt jeremyfelt reopened this Aug 26, 2014

@danielbachhuber

This comment has been minimized.

Contributor

danielbachhuber commented Aug 26, 2014

Is this worth bumping the memory limit by default?

Yes humanmade/Salty-WordPress#103

@simonwheatley

This comment has been minimized.

Contributor

simonwheatley commented Aug 26, 2014

Agreed. 512 is pretty low, given this is aimed at "a common configuration for working with high traffic WordPress sites".

@lkwdwrd

This comment has been minimized.

Contributor

lkwdwrd commented Aug 26, 2014

I've upped mine to 2048.. I wouldn't mind a higher default.

Luke Woodward – Senior Strategic Engineer
10up LLC http://10up.com | luke.woodward@10up.com | @lkwdwrd

On Tue, Aug 26, 2014 at 9:57 AM, Daniel Bachhuber notifications@github.com
wrote:

Is this worth bumping the memory limit by default?

Yes humanmade/Salty-WordPress#103
humanmade/Salty-WordPress#103


Reply to this email directly or view it on GitHub
#427 (comment)
.

jeremyfelt added a commit that referenced this issue Sep 4, 2014

Bump VirtualBox VM memory allocation to 1024 from 512
1GB seems to be a nicer answer than 512MB by default. A Customfile
can be used to reduce or raise the memory footprint to another
level.

Fixes #427
@zamoose

This comment has been minimized.

Contributor

zamoose commented Sep 4, 2014

One small interjection:
1024 SUCKS on laptops with 4GB of RAM. 512 was a good default, at least for
mobile apps. Maybe the docs should reflect this and advise a customfile for
such users?

On Thu, Sep 4, 2014 at 12:14 PM, Jeremy Felt notifications@github.com
wrote:

Closed #427 #427
via #439 #439.

Reply to this email directly or view it on GitHub
#427 (comment)
.

-Doug

@jeremyfelt

This comment has been minimized.

Member

jeremyfelt commented Sep 4, 2014

Maybe the docs should reflect this and advise a customfile for such users?

This is a good idea. We can find a way to link to https://github.com/Varying-Vagrant-Vagrants/VVV/wiki/Customising-your-Vagrant's-attributes-and-parameters in the README.

I'd also like to find a way to make a few of these things customizable through a config (YAML) file of sorts that can be excluded from git.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment