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
I am using the newest version of VsCode, hdl_checker-extension and hdl_checker-client. (Windows10)
As linter I use the ModelSim vcom.
It works good, while working on opened vscode and editing my vhdl-files.
Bug: As soon as I close vscode completely, the "hdl_checker-script.py" invokes on closing.
This script leads to aprox. 15% cpu-usage and cannot terminate itself anymore; of course not, as the hdl_checker-client terminates, when closing vscode also.
I have to close this process by myself.
I think, hdl_checker tries to do another fresh build, when closing vscode - thus starting the mentioned script:
The horrorible part is, after closing vscode, and opening vscode again, and repeating the steps above, another python-process starts, which invokes a further "hdl_checker-script.py".
Resulting into even more cpu-load.
Please, fix this behaviour.
Thx.
Greetings.
The text was updated successfully, but these errors were encountered:
Hi,
I am using the newest version of VsCode, hdl_checker-extension and hdl_checker-client. (Windows10)
As linter I use the ModelSim vcom.
It works good, while working on opened vscode and editing my vhdl-files.
Bug: As soon as I close vscode completely, the "hdl_checker-script.py" invokes on closing.
This script leads to aprox. 15% cpu-usage and cannot terminate itself anymore; of course not, as the hdl_checker-client terminates, when closing vscode also.
I have to close this process by myself.
I think, hdl_checker tries to do another fresh build, when closing vscode - thus starting the mentioned script:
The horrorible part is, after closing vscode, and opening vscode again, and repeating the steps above, another python-process starts, which invokes a further "hdl_checker-script.py".
Resulting into even more cpu-load.
Please, fix this behaviour.
Thx.
Greetings.
The text was updated successfully, but these errors were encountered: