Skip to content

Constant crashing due to "unexpected synthetic: SyntheticSyntax" #16712

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

Closed
ThomasMiz opened this issue Feb 29, 2024 · 4 comments
Closed

Constant crashing due to "unexpected synthetic: SyntheticSyntax" #16712

ThomasMiz opened this issue Feb 29, 2024 · 4 comments
Labels
C-bug Category: bug

Comments

@ThomasMiz
Copy link

A few days ago, rust-analyzer started behaving a bit weird and taking longer than usual. Today it's been crashing nonstop all day, I even uninstalled everything and re-installed with rustup, and the behavior persisted. At one point today every character I typed caused another worker thread panic message.

I have tried to create a minimum reproducible example, but this odd behavior seems to follows no God, much less listens to mortals. I am using VS Code, I've tried adding "rust-analyzer.trace.server": "verbose" and "rust-analyzer.cargo.extraEnv": {"RA_LOG": "info", "RUST_BACKTRACE": "full" } to settings.json but even after a restart this seemed to have no effect. Still, I have captured the stderr output into a file here.

This file holds the output of around an hour of usage. It seems to be particularly angry about me using the Result enum, multiple of the crashes were when typing Result::something.

If there's anything else I can provide to help, do let me know! Thank you! 😊

rustc version: 1.76.0 (07dca489a 2024-02-04)
rust-analyzer version: 0.3.1860-standalone (5346002 2024-02-25)

@ThomasMiz ThomasMiz added the C-bug Category: bug label Feb 29, 2024
@Young-Flash
Copy link
Member

Young-Flash commented Feb 29, 2024

try the lastest nightly release to see whether #16684 fix this issue

@ThomasMiz
Copy link
Author

Fixed in #16684, try the lastest nightly release

Excellent! Should I close this issue?

@Young-Flash
Copy link
Member

let's close if it does fixed

@ThomasMiz
Copy link
Author

Sure! I'm on nightly now, I'll let you know how it goes. It's definitely behaving better than before 😅

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

No branches or pull requests

2 participants