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

ols "out of range" crashing on Windows 11 #607

Open
adambigg-s opened this issue Feb 25, 2025 · 2 comments
Open

ols "out of range" crashing on Windows 11 #607

adambigg-s opened this issue Feb 25, 2025 · 2 comments

Comments

@adambigg-s
Copy link

adambigg-s commented Feb 25, 2025

I am using the Helix text editor on Windows 11 with ols built from the master branch. Every time, as soon as I invoke "goto_definition" my editor instantly crashes. The last entries in the log are as follows:

2025-02-25T00:44:30.140 helix_lsp::util [WARN] LSP position Position { line: 66, character: 0 } out of range assuming EOF
2025-02-25T00:44:30.711 helix_term::application [ERROR] Ignoring unknown notification from Language Server: protocol error: InvalidParams: Invalid params: invalid value: integer `-1`, expected u32.

I believe that, because the call is coming from "inside" my editor, if that makes sense, that this is causing Windows 11 to flag Helix as malware because it is entirely deleting the executable. Even upon rebuilding, without wiping all cache, I get some error saying:

Program 'hx.exe' failed to run: Operation did not complete successfully because the file contains a virus or potentially unwanted softwareAt line:1 char:1 + hx + ~~.

I am even trying to read through the ols source seeing if I can find why this is occurring, but so far I have no idea what the issue is. Has anyone else experience this or know a way to fix it? As of right now, I am just writing Odin with no LSP. This problem occurs as soon as I invoke anything ols exclusively, even though there is not much indication from the error messages that this is an ols problem, I have confirmed it is only happening when ols gets called and is added to $PATH for use.

@DanielGavin
Copy link
Owner

What happens if you call ols version?

@adambigg-s
Copy link
Author

What happens if you call ols version?

I get "dev-2024-11-9:g584f01b"

For the past couple of hours, since I initially posed, I changed to the nightly release and I have yet to have a crash. While the versions for both say the same, building from master has some newer commits so as of right now it seems to be an issue that is from after Jan 26th, 2025. I'll keep experimenting, and later I will rebuild master and see if the problem immediately starts occurring again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants