From fbe2a5e7264f235294fee565c13ffaba1e46285e Mon Sep 17 00:00:00 2001 From: Louis Lagrange Date: Wed, 28 Oct 2015 20:14:23 +0100 Subject: [PATCH 1/3] Add "out of memory" tip --- doc/articles/troubleshooting.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index a6f082ab7..9120c0cc5 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -100,7 +100,9 @@ If composer shows memory errors on some commands: `PHP Fatal error: Allowed memory size of XXXXXX bytes exhausted <...>` -The PHP `memory_limit` should be increased. +Check first that XDebug is not loaded in your `php.ini` by running `composer diagnose`. If XDebug is loaded, you should disable it by commenting the line `zend_extension=path/to/xdebug` in your `php.ini`. Don't forget to enable XDebug again after using Composer, if you need it. + +If composer still raises the error, the PHP `memory_limit` should be increased. > **Note:** Composer internally increases the `memory_limit` to `1G`. > If you have memory issues when using composer, please consider [creating From 3df536a3ba5e7e85b9e40bb598032d2118dec65c Mon Sep 17 00:00:00 2001 From: Louis Lagrange Date: Thu, 29 Oct 2015 13:29:33 +0100 Subject: [PATCH 2/3] Wrap lines at the correct limit Assuming this limit is 80 cols. --- doc/articles/troubleshooting.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index 9120c0cc5..1890b4c10 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -100,7 +100,10 @@ If composer shows memory errors on some commands: `PHP Fatal error: Allowed memory size of XXXXXX bytes exhausted <...>` -Check first that XDebug is not loaded in your `php.ini` by running `composer diagnose`. If XDebug is loaded, you should disable it by commenting the line `zend_extension=path/to/xdebug` in your `php.ini`. Don't forget to enable XDebug again after using Composer, if you need it. +Check first that XDebug is not loaded in your `php.ini` by runnin +`composer diagnose`. If XDebug is loaded, you should disable it by +commenting the line `zend_extension=path/to/xdebug` in your `php.ini`. +Don't forget to enable XDebug again after using Composer, if you need it. If composer still raises the error, the PHP `memory_limit` should be increased. From 842e09a1436da766b1f2107f8a2af99aebe05244 Mon Sep 17 00:00:00 2001 From: Louis Lagrange Date: Thu, 29 Oct 2015 13:32:12 +0100 Subject: [PATCH 3/3] Typo --- doc/articles/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/articles/troubleshooting.md b/doc/articles/troubleshooting.md index 1890b4c10..8e5d9afb0 100644 --- a/doc/articles/troubleshooting.md +++ b/doc/articles/troubleshooting.md @@ -100,7 +100,7 @@ If composer shows memory errors on some commands: `PHP Fatal error: Allowed memory size of XXXXXX bytes exhausted <...>` -Check first that XDebug is not loaded in your `php.ini` by runnin +Check first that XDebug is not loaded in your `php.ini` by running `composer diagnose`. If XDebug is loaded, you should disable it by commenting the line `zend_extension=path/to/xdebug` in your `php.ini`. Don't forget to enable XDebug again after using Composer, if you need it.