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 tried using the vscode extension while working on Luminol which is a relatively large codebase (~50k lines of code)
rustowl spun up and used 100% of my CPU for about 5 minutes before I decided to close vscode
After closing vscode, rustowl didn't stop and I had to manually kill all of its processes with pkill
The text was updated successfully, but these errors were encountered:
@melody-rs Thank you for pointing out the performance issue.
I'm aware of this issue, but it's difficult to fix. (I'm already using multi-threading where possible.)
I will implement a forced task kill when the LSP server receives a shutdown command.
We have implemented automatic shutdown for rustowlc.
However, we currently have no fundamental ideas for optimizing RustOwl.
So, we have left this as future work. Thank you for your report.
I tried using the vscode extension while working on Luminol which is a relatively large codebase (~50k lines of code)
rustowl spun up and used 100% of my CPU for about 5 minutes before I decided to close vscode
After closing vscode, rustowl didn't stop and I had to manually kill all of its processes with
pkill
The text was updated successfully, but these errors were encountered: