Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

ioncube + xcache on PHP 5.5 Allowed memory size of 536870912 bytes exhausted #83

Open
gpsa opened this issue Dec 7, 2014 · 1 comment

Comments

@gpsa
Copy link

gpsa commented Dec 7, 2014

When xcache + ioncube extensions are enabled on PHP 5.5, and I start php embedded web server, se what happens with apigility:

php -S 0.0.0.0:8080 -t /var/www/zend/apigility/v.1.4.0/public /var/www/zend/apigility/v.1.4.0/public/index.php

PHP 5.5.19 Development Server started at Sun Dec 7 01:33:35 2014
Listening on http://0.0.0.0:8080
Document root is /var/www/zend/apigility/v.1.4.0/public
Press Ctrl-C to quit.
[Sun Dec 7 01:33:37 2014] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 140645686686384 bytes) in Unknown on line 0


( ! ) Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 140645686686384 bytes) in Unknown on line 0

I saw this together Matthew Weier, in PHPConferenceBR. He he taught me xcache is not necessary if I use PHP 5.5, whereas in this version, PHP comes with Opcache.
Is not in fact a problem, but is a good thing to know why it happens.

weierophinney added a commit to weierophinney/zf-apigility that referenced this issue Jul 9, 2015
This patch provides a new class, `ZF\Apigility\Application`, which
extends `Zend\Mvc\Application` to provide a try/catch block around the
route event. This addresses the concerns raised in zfcampus#83, as it means any
exception raised by a route listener will be caught and lead to
triggering the `dispatch.error` event. In the case of Apigility
applications, this will allow us to return problem details.
weierophinney added a commit to weierophinney/zf-apigility that referenced this issue Jul 14, 2015
This patch provides a new class, `ZF\Apigility\Application`, which
extends `Zend\Mvc\Application` to provide a try/catch block around the
route event. This addresses the concerns raised in zfcampus#83, as it means any
exception raised by a route listener will be caught and lead to
triggering the `dispatch.error` event. In the case of Apigility
applications, this will allow us to return problem details.
@michalbundyra
Copy link
Member

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at laminas-api-tools/api-tools#56.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants