You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parameter intelephense.maxMemory is not working when Intelephense is used on remote server through SSH. I tried to set intelephense.runtime but I have the tooltip "This setting cannot be applied in this window. It will be applied when you open a local window." (didn't have the same tooltip on maxMemory).
To Reproduce
Set max memory to the minimum in vscode settings :
"intelephense.maxMemory": 256,
Run a Laravel project on a server then open the project with in vscode with Remote SSH.
View RAM used in Help > Open Process Explorer
Expected behavior
I would like the memory limit working also on remote server.
Screenshots
Here an example with 3 projets laravel opened and with a limit to 1024 MB :
Platform and version
Local system :
Linux Mint 21
VSCode : 1.95.3
Intelephense : 1.12.6 (with paid licence)
Remote server (using SSH) :
Debian 12
Thanks in advance and for your awesome plugin !
Best regards, Max
The text was updated successfully, but these errors were encountered:
Describe the bug
The parameter intelephense.maxMemory is not working when Intelephense is used on remote server through SSH. I tried to set intelephense.runtime but I have the tooltip "This setting cannot be applied in this window. It will be applied when you open a local window." (didn't have the same tooltip on maxMemory).
To Reproduce
Set max memory to the minimum in vscode settings :
Run a Laravel project on a server then open the project with in vscode with Remote SSH.
View RAM used in Help > Open Process Explorer
Expected behavior
I would like the memory limit working also on remote server.
Screenshots
Here an example with 3 projets laravel opened and with a limit to 1024 MB :
Platform and version
Local system :
Remote server (using SSH) :
Thanks in advance and for your awesome plugin !
Best regards, Max
The text was updated successfully, but these errors were encountered: