Check the screenshot.

So far what we know is that it happens:

1. when you're connected
2. there are some warnings in the sidepanel
3. scope is set to Current File
4. and you're actively editing a query, like in screenshot

We don't have the stack trace so we will have to try and reproduce this first and then attempt getting the stack trace from there.

Without a stack trace - our best guess is that if in Current File scope - we're anyhow using `CachedQueryService.queryAt` method or anything that traverses PsiElement tree on every key stroke then that might be a good starting point.