-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension causes high cpu load #129
Comments
How big was the graph you tried to render? |
The extension has started locking up itself and other vscode extensions for me when previewing a .dot file it previously was able to render ~10 months ago. I can't help but wonder if this is a vscode issue. Perhaps it's stricter now in killing extensions that are CPU-hungry.
After some testing of various graphs I have lying around:
I see this frequently:
And sometimes this:
Finally, here's the profiling information that vscode really wants me to attach: tintinweb.graphviz-interactive-preview-unresponsive.cpuprofile.txt |
I've only started using the extension today and it locks up so frequently ( The hangs tend to happen more when the preview window is open, so it looks like a recurrence of (or has the same core issue as) #138. And maybe 50% of the time when I reopen vscode, the extension fails to show any preview, with the
|
Just leaving my two cents that I am experiencing the same issues described by @Zannick from two weeks ago. Seems like a great extension aside from this issue. |
Any news for this? Having the same issue. Ext version: |
Performance
graphviz-interactive-preview
0.3.1
Windows_NT x64 10.0.19044
1.70.1
file:///c%3A/Users/NOOELAN/AppData/Local/Temp/tintinweb.graphv [tintinweb.graphviz-interactive-preview-unresponsive.cpuprofile.txt](https://github.com/tintinweb/vscode-interactive-graphviz/files/9350987/tintinweb.graphviz-interactive-preview-unresponsive.cpuprofile.txt) iz-interactive-preview-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load
The text was updated successfully, but these errors were encountered: