-
Notifications
You must be signed in to change notification settings - Fork 663
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
Fatal error since PHP 8.3.9+ #11067
Comments
got the same error running psalm 5.25.0 on PHP 8.2.22 |
Last known good: 5.6.0 (broken since 5.7.0). |
Maybe stating the obvious, but this is neither a problem exceeding the max execution time nor a PHP config issue. It's an infinite loop. |
I can't reproduce it. Running latest 5.x branch on either PHP 8.2.23 or PHP 8.3.11 (both are the latest versions at the time of writing) on Psalm's own source code. |
I can reproduce this using PHP 8.3.11 (brew, Mac M1), when running it with |
Running linux here, and it looks like it may be apple-specific: php/php-src#12814 (comment) @vudaltsov have you had any success tracking it down? |
I have PHP 8.3.11 installed with brew on a MacBook Pro M1 too. The |
I started experiencing this after upgrading my project from PHP8.1 to 8.2. If I add |
If you actually find this slow you could remove it because it's just a visual bug really.
Can confirm what @bakert suspects. On my end, however, I've not changed PHP versions for quite some time, nor have I changed psalm versions (am on 4.30.0). My suspicion is that this started when I upgraded to Sequoia 15.1. --threads=1 works, --threads=2 does not.
|
same problem on M2 + php8.3 + --threads != 1 |
When I run the whole analyze, I got the following error at the very end:
PHP Fatal error: Maximum execution time of 0 seconds exceeded in vendor/vimeo/psalm/src/Psalm/Internal/Type/ParseTree.php on line 26
If I remove the method
ParseTree::__destruct
, the error disappear. This method seems to exist for the memory management, but I do not see any improvement of the memory usage with or without the destructor.The text was updated successfully, but these errors were encountered: