Hello,
I have been using SysIDE with Academic License for the last months (last time was last week) VS Code and everything was working fine.
Today VS Code is giving me these errors when I open a .sysml file:
- Syside client: couldn’t create connection to server.
- Restarting server failed
- Message: bad allocation: Code: -32603
Tom Sawyer Visualiser still works perfectly.
Editor features (e.g., outline, colors, errors checkl) are not working anymore.
Do you have any suggestions on how I can solve these problems?
Thanks
Thanks for the report. Does this happens all the time, even in a minimal workspace with a single .sysml file?
Hi Daumantas,
In a minimal workspace, it works. The workspace I was working with was unnecessarily full of .sysml files.
Thanks for the help!
The workspace I was working with was unnecessarily full of .sysml files.
Even then I would like to fix the unexpected error. Is the workspace on some shared or network drive as opposed to Windows drive, e.g. C:/? Otherwise, can you share the workspace so I could try reproducing the issue?
The workspace path is C:\Folder01\Folder02 (Windows).
I was sending you the workspace, when I was able to isolate the problem. The problem was caused by an old Python virtual enviornment folder I haven’t activated in months. If you want I can send it to you.
As I removed it, the SysIDE tools started to work again.
That would be great. Tried locally on a Windows VM with limited memory and a relatively large/deep folder including python venv but could not reproduce.
Thanks, I can reproduce the issue. Seems to be an issue due to too many open file handles. In the meantime, this can be fixed by either prefixing unnecessary directories with . to ignore them during workspace search, or adding paths/globs to syside.exclude.
1 Like
Fixed for the next release. Directory snapshots failed to read without an error set on large directories, and the backing buffer kept growing uncontrollably until crashing with bad_allocation.
1 Like