rust-lang / rust-lang/rust-analyzer
latest version will cause emacs/rustic with eglot cpu 100% forever when open core library
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
I can't reproduce this on other project, including std.
But when I open the core library by goto defination on a type, it happens 100%
It is emacs process eating CPU, but with older RA, this never happens.
So, I don't know whether is an emacs bug or RA returned something to emacs causing it busy for ever
The library is the one shipped with stable 1.81.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report in Emacs with rustic and eglot: open the Rust 1.81 stable core library through goto definition and compare current rust-analyzer with an older version. Determine whether rust-analyzer's response or Emacs enters the endless CPU loop; done means the core-library navigation no longer drives Emacs to 100% CPU.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- emacs, rust
- Domain
- compilers, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100