Bug #48809 [PATCH]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
From: seocontentmachine11@gmail.com Date: Fri, 12 Mar 2021 02:45:42 +0000 Subject: Bug #48809 [PATCH]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c References: 1 Groups: php.bugs Request: Send a blank email to php-bugs+get-232663@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=48809&edit=1
ID: 48809
Patch added by: seocontentmachine11@gmail.com
Reported by: ibboard at gmail dot com
Summary: "virtual memory exhausted: Cannot allocate memory"
with libmagic/apprentice.c
Status: Wont fix
Type: Bug
Package: Compile Failure
Operating System: CentOS 4
PHP Version: 5.3.0
Block user comment: N
Private report: N
New Comment:
The following pull request has been associated:
Patch Name: Update Swoole ini
On GitHub: https://github.com/php/doc-en/pull/486
Patch: https://github.com/php/doc-en/pull/486.patch
Previous Comments:
------------------------------------------------------------------------
[2021-03-06 15:29:50] vcd50802 at zwoho dot com
"Quite a bit" of memory? That seems like a bit of an understatement when it will quite
happily consume over 350MB of memory on a single file and previous versions of PHP could be compiled
in ~150MB or less (albeit without that extension) :D
Maybe libmagic needs disabling as a default module if it was in PECL before and is known to causes
problems with older compilers?
How much memory am I expected to need to compile it if it fails with 350MB? I've just watched
'top' while the compile continued and it maxed out at ~120MB without libmagic, which is
far more reasonable.
http://images.google.pt/url?sa=t&url=https://www.news000k.com/2020/05/Elantra.html
http://images.google.pt/url?sa=t&url=https://www.news000k.com/2020/05/Maserati.html
http://images.google.pt/url?sa=t&url=https://www.news000k.com/2020/05/Golf.html
http://images.google.pt/url?sa=t&url=https://www.news000k.com/2020/06/BMW.html
------------------------------------------------------------------------
[2021-02-03 16:50:37] cttratamentodroga at gmail dot com
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
<a href="https://www.fluocomunicacao.com.br/">agencia
de marketing digital</a>and the instructions on how to report
a bug at <a href="https://www.fluocomunicacao.com.br/">agencia
de marketing digital</a>
This is the correct behaviour.
------------------------------------------------------------------------
[2021-02-03 16:50:16] cttratamentodroga at gmail dot com
Thank you for taking the time to write to us, but this is not<br>a bug. Please double-check
the documentation available at<br><a href="https://www.ctsaudepremium.com.br/"
rel="nofollow">clinica de recuperação</a> and the instructions on how to
report<br>a bug at <a href="https://www.ctsaudepremium.com.br/"
rel="nofollow">clinica de recuperação</a>
a
------------------------------------------------------------------------
[2021-02-03 16:48:20] cttratamentodroga at gmail dot com
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
<a href="https://www.fluocomunicacao.com.br/">agencia
de marketing digital</a>and the instructions on how to report
a bug at <a href="https://www.fluocomunicacao.com.br/">agencia
de marketing digital</a>
This is the correct behaviour.
------------------------------------------------------------------------
[2021-02-03 16:47:55] fluo at fluocomunicacao dot com dot br
Thank you for taking the time to write to us, but this is not<br>a bug. Please double-check
the documentation available at<br><a href="https://www.ctsaudepremium.com.br/"
rel="nofollow">clinica de recuperação</a> and the instructions on how to
report<br>a bug at <a href="https://www.ctsaudepremium.com.br/"
rel="nofollow">clinica de recuperação</a>
a
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=48809
--
Edit this bug report at https://bugs.php.net/bug.php?id=48809&edit=1
Thread (38 messages)
- #48809 [Opn->WFx]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- #48809 [WFx]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- #48809 [WFx]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- #48809 [WFx]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- #48809 [WFx]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [PATCH]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
- Bug #48809 [Com]: "virtual memory exhausted: Cannot allocate memory" with libmagic/apprentice.c
| « previous | php.bugs (#232663) | next » |
|---|