Skip to content
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

json_decode() can go OOM when processing larger files #492

Closed
fichtner opened this issue Dec 3, 2015 · 5 comments
Closed

json_decode() can go OOM when processing larger files #492

fichtner opened this issue Dec 3, 2015 · 5 comments
Assignees
Labels
upstream Third party issue
Milestone

Comments

@fichtner
Copy link
Member

fichtner commented Dec 3, 2015

In a recent crash report, a 20 MB file is expanded to several hundreds of MB, first hitting memory limits, and if memory limits are lifted, processing timeouts. CANNOT COMPUTE. :)

@fichtner fichtner added the feature Adding new functionality label Dec 3, 2015
@fichtner fichtner added this to the 16.1 milestone Dec 3, 2015
@fichtner fichtner modified the milestones: 16.7, 16.1 Dec 31, 2015
@fichtner fichtner self-assigned this Dec 31, 2015
@fichtner
Copy link
Member Author

This may be fixed in PHP 7, bumping to 16.7.

@AdSchellevis
Copy link
Member

I would definitely want to test that, PHP 7 will provide some other improvements as well, but will also bring quite some backward incompatible changes.

@fichtner
Copy link
Member Author

FreeBSD ports are not there yet anyway. Lots of time. :)

@fabianfrz
Copy link
Member

At the moment (8.1.2016) PHP 7 cannot be used because phalcon is not compatible.

phalcon/cphalcon#10378

@fichtner fichtner added upstream Third party issue and removed feature Adding new functionality labels Feb 16, 2016
@fichtner fichtner modified the milestones: Future, 16.7 Feb 16, 2016
@fichtner fichtner modified the milestones: 17.1, Future Jul 1, 2016
@fichtner
Copy link
Member Author

First test build for PHP 7.0 is done, this is queued up for 17.1. No need to keep this reminder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Third party issue
Development

No branches or pull requests

3 participants