New Memory Manager for PHP7

[dstogov]

New MM performance impact

[laruence]

👍

[76200]

How about SF2?

[dstogov]

what is SF?

Dmitry.

On Fri, Aug 22, 2014 at 3:38 PM, bartek notifications@github.com wrote:

How about SF2?

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

[yosymfony]

SF2 = Symfony Framework 2

[php-pulls]

Comment on behalf of nikic at php.net:

Closing as this has been merged.

[hikari-no-yume]

Ignore my deleted comment, it is probably not your fault.

[dstogov]

Hi Andrea,

I don't know about any errors in new MM.
The line where it crashes may be helpful.

Most probably it's related to some memory corruption.
Try to run the same code with valgrind and USE_ZEND_ALLOC=0.
It it reports any errors, the problem must be unrelated to new MM.

Thanks. Dmtiry.

On Thu, Aug 28, 2014 at 2:03 AM, Andrea Faulds notifications@github.com
wrote:

[11:01pm] ajf: I wonder if an error I’m having is dstogov’s new memory
manager’s fault
[11:01pm] ajf: It’s really, really bizarre
[11:01pm] ajf: According to valgrind:
[11:01pm] ajf: 1) I try to decrement a bigint,
[11:01pm] ajf: 2) zend_bigint_init_alloc() is called to init and alloc a
new bigint,
[11:01pm] ajf: 3) zend_bigint_alloc() is called to alloc the new bigint,
[11:02pm] ajf: 3) it calls emalloc()
[11:02pm] ajf: 5) emalloc() calls zend_mm_alloc_heap()
[11:02pm] ajf: 6) emalloc() calls zend_mm_alloc_small()
[11:02pm] ajf: 7) segfault

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

[hikari-no-yume]

Yeah, @dstogov it looks like something else is going on, it just so happened the new MM make it segfault while memory silently corrupted with the old one.