0001535: Laravel causes PHP warning (exception not caught) xdebug enabled, otherwise all is fine

ID	Project	Category	View Status	Date Submitted	Last Update
0001535	Xdebug	Uncategorized	public	2018-03-14 20:48	2019-06-28 11:18

Reporter	amenk	Assigned To
Priority	normal	Severity	major	Reproducibility	always
Status	resolved	Resolution	duplicate
Platform	Linux	OS	Ubuntu	OS Version	16.04.3
Product Version	2.6.0
Target Version	2.6.1

Summary	0001535: Laravel causes PHP warning (exception not caught) xdebug enabled, otherwise all is fine
Description	With xdebug enabled I can reproduce an error: PHP Warning: Uncaught League\Flysystem\Plugin\PluginNotFoundException: Plugin not found for method: read in /tmp/laravel/vendor/league/flysystem/src/Plugin/PluggableTrait.php:49 without xdebug on, everything runs fine.
Steps To Reproduce	composer create-project laravel/laravel cd laravel composer require proengsoft/laravel-jsvalidation php artisan vendor:publish --provider="Proengsoft\JsValidation\JsValidationServiceProvider" --tag=public --force (I will try to make a smaller example)
Additional Information	Not reproducible with 7.1.8-2+ubuntu16.04.1+deb.sury.org+4 Reproducible after update to 7.1.18 See here https://stackoverflow.com/questions/49281490/laravel-causes-php-warning-exception-not-caught-xdebug-enabled-otherwise-all
Tags	No tags attached.

Operating System
PHP Version	7.1.15-7.1.19

amenk 2018-03-14 20:49 reporter ~0004613	bye the way ... the stack trace from the warning is enormous (not ending)

amenk 2018-03-14 20:50 reporter ~0004614	With php7.2 it works fine, maybe we just ignore the bug and switch to 7.2.3 :-)

amenk 2018-03-14 20:59 reporter ~0004615	without my setting xdebug.collect_params=4 it works fine. so I will be more careful with that in the future. I think it is fine, that xdebug runs out of memory. A nicer error message would be cool,recommending to lower such settings. The real bug is, that the exception is not caught properly while it is, when xdebug is on.

derick 2018-03-15 11:07 administrator ~0004616	The real bug is is that Xdebug is reading variables that are already freed while constructing the exception stack traces. These variables are only read with xdebug.collect_params > 0. Reading already freed memory means all kinds of weird things can happen, and your errors are one of the symptoms, but I expect there to be many more.

Xenos 2019-05-15 16:33 reporter ~0005024	If that's so, I suppose again that the PR for 0001665 ( https://github.com/xdebug/xdebug/pull/473 ) should fix this too?

derick 2019-06-28 11:18 administrator ~0005041	Closing this as duplicate of 0001665