derfony Here's the stack trace: https://zerobin.net/?57df9977c1161328#im6ek81T+bFV7PSZ4uORtPwu8QmJoNMbM7FPILcHZrM=
Stack overflow in Symfony project
derfony thank you! I'll try to release the fix within today
derfony we have fixed the code that causes this; however, we don't have any reproducible test cases.
Basically, there will be a very long expression in your workspace; I'd assume a string concatenation (thousands of .
) or another binary operator. This is probably in some generated PHP code.
We'll try to make such code and test the rest of the extension to see if it survives.
JakubMisek Thanks for your reply. I'm working on TYPO3-projects using Docker and DDEV. TYPO3 generates PHP-files that it caches in a temporary directory that resides withinside the workspace root. I tried emptying the respective folder (as it will be regenerated once any of the TYPO3-code is called anyway) and this helped me to start VSCode without the PHP Language Server crashing.
JakubMisek Now I've upgraded a project to a different TYPO3 Version (11LTS instead of 10LTS) and removing the generated code in var/cache
inside the workspace root does not help anymore. PHP version remained the same with 7.4.33. The PHP-Language-Server still works in projects using TYPO3 10LTS. Here's the stack trace: https://zerobin.net/?918a8a2a1dbbb220#wBP732OAH4+NRokthIgWE9pFGlXowxUFjnn+AD5gr6k=
derfony thank you for the update, and for the stack trace!
I'll try to fix it within the next update.
derfony Do you have the latest version, we should have fixed that on January '23 :/
JakubMisek Thanks @JakubMisek for again looking into the issue. I have version v1.26.11866 installed, from January 9th.
derfony the current version is 1.33
. I strongly recommend updating https://marketplace.visualstudio.com/items/DEVSENSE.phptools-vscode/changelog
JakubMisek My VSCode tells me there are no extensions to update. Weird. Will look into that, thanks for your help!
JakubMisek I'm now running 1.33
. For the moment it has resolved the issue. Naturally I'll keep an eye on it. Many thanks for your quick support!
derfony thank you for trying the update, I'll be happy for any other feedback :)
JakubMisek Hi Jakub, here's another stack trace: https://zerobin.net/?9462ce76ce9dec98#stFm2QvzXpvRSsvFbzsEJ5n/ys1n2CIwQ+vLunmq35c=
As you can see in the trace, I'm now running 1.33.12934
. So what happens? For the workspace I'm working on I set "php.problems.scope": "user",
and also set "files.watcherExclude"
to "**/var/**": true,
(as this is the directory, that while running the TYPO3-installation using ddev and docker will contain generated code) although I'm not sure this has any effect on the php tools. After starting VSCode with this workspace files will now be scanned quietly in the background, the number of files that contain problems like calls of deprecated functions and are marked in the filebrowser grows, as does the number of problems in the problems tab of the bottom panel. Now when I open any php file the language server crashes. When I scroll through the file the server crashes again and again until it is eventually shut down.
- Edited
derfony Thank you! will be fixed
note for me:
at Devsense.PHP.Syntax.TreeVisitor.VisitBinaryEx(Devsense.PHP.Syntax.Ast.BinaryEx)
at Devsense.PHP.Refactoring.Visitors.ContextVisitor.VisitElement(Devsense.PHP.Syntax.Ast.ILangElement)
derfony preparing a pre-release version with fix soon
- Edited
Hi @JakubMisek ,
I also stumbled across a similar issue, starting randomly yesterday evening.
The only thing I can imagine that might has a relation to this is adding javascript to my project. However, I don't belive this is the problem.
I am currently running on a trial for the premium, as I thought about buying the full license, but this was activated today because I thought the issue might be related somehow with not being premium.
https://bin.uhl.cloud/?08352741bfa11a40#8GriUVd9wnXTk963A13KXVNtb3KA5iY42Uzqb95BAUVu
Would be nice to get a quick support on this one :).
// Luca
LucaWelker thank you very much for the log; I'll take a look if we can fix it quickly.
LucaWelker just released pre-release 1.42.14700
which fixes related issues; it should fix this one as well.
Please let me know if it helps. Thanks!
Hi @JakubMisek,
thanks a lot for you efforts and quick reaction.
However it seems that the fix didn't work out for me, as you can see in the following stack trace:
https://bin.uhl.cloud/?11d5adf619a769d9#DSfWtpGPeGUnXd5b6y5CvZ1UwZTZBPQZrJgVryHC7LPG
Kindest,
Luca
LucaWelker you're right, we didn't push this change into the pre-release yet - working on it! thank you!