[jb] changes to Xmx in low memory notification are not applied on restart
Open
Nobody has claimed this yet.
aspect: performance
editor: jetbrains
meta: never-stale
type: bug
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 1.4k
- Avg merge
- 17h 58m
- Merged PRs (30d)
- 5
Description
Bug description
Steps:
- emulate low memory notification with: https://gitpod.io/#INTELLIJ_VMOPTIONS=-Xmx384m/https://github.com/eclipse/xtext-core
- open with IntelilJ, and wait when JDK indexing is done, after that try to use language smartness
- click upgrade Xmx in notification and follow up with restart
- it restarts, reconnects, but Xmx is not changed
Also verify upgrade in the backend control center.
Steps to reproduce
See above.
Workspace affected
No response
Expected behavior
No response
Example repository
No response
Anything else?
No response
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 low-memory notification flow with the provided Gitpod and IntelliJ steps, then inspect the restart behavior and the backend control center's reported Xmx value. Done means selecting “upgrade Xmx” persists the changed value after restart and the backend control center reflects the upgrade.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100