How to debug high CPU ? #77
Description
Summary
Upon startup, extension mostly just sits there occupying 100% of one core. After closing vscode it takes several seconds for the extension process to exit.
Relevant information
I have had the extension working occasionally and love it when it does. Mostly it just seems to be stuck in a loop.
Running linux (mix of ubuntu/debian stable) with v2.11.1 from the marketplace. Workspace has a lot of files that throw parsing errors (backslash commands in them for psql). These errors are shown in the output panel you can display at the bottom of the editor. After startup no further messages are logged here.
Possibly relevant points:
- It makes no difference whether I set correct or incorrect connection details in the extension settings.
- When db connections are present, they would be over a (virtual) network to a containerised db.
- The workspace does have a lot of SQL files although I'm only interested in it operating on the files I have opened.
- I have added ".sql" as one of the extensions it will recognise
I don't know how I can dig any deeper into the problem - some verbose debugging mode I can enable or similar. Keen to do what I can to diagnose this. TIA.