Skip to content
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

Slow performance and broken tabbing #8

Open
2 tasks done
Wuerfel21 opened this issue Apr 21, 2024 · 3 comments
Open
2 tasks done

Slow performance and broken tabbing #8

Wuerfel21 opened this issue Apr 21, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@Wuerfel21
Copy link

and have you...

  • I updated to the latest spin2 version available
  • I have restarted VSCode and the problem still exists

Version of Spin2 Language Server VScode Extension with the issue

I think it started happening in the last version?

Is this a regression?

Yes. This used to work, but now it doesn't.

Hardware, Operating System, Operating System version, VSCode version

Hardware:
OS Ver:
VSCode Ver: VSCodium 1.85.1 (yea I should probably update it one of those days)

Description of problem

Since the last version or two, there have been issues where the language server is extremely slow to respond and the semantic highlights will stay outdated for multiple seconds and the whole editor becomes somewhat sluggish. Also sometimes the symbol information disappears.

Also, at some point the tabbing stopped working at all. I have no idea.

Could also be because the file I'm mostly working on is getting really long now.

Additional information

Very long file I'm currently working on:
misoyume_lower.spin2.zip

@Wuerfel21 Wuerfel21 added the bug Something isn't working label Apr 21, 2024
@ironsheep
Copy link
Owner

I"ll give the highlighting of unused code a workout and see what we find. Also tabbing. More soon

@ironsheep ironsheep self-assigned this May 8, 2024
@ironsheep
Copy link
Owner

I found the cause for the broken tabbing... fixes will appear in the next release.

@Wuerfel21
Copy link
Author

Something I notice when there are slowdowns is that it appears that all processing freezes for a bit and then it quickly runs through all the changes that have happened in the meantime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants