microsoft / microsoft/copilot-for-eclipse
[Bug] UI Freeze when starting Eclipse IDE
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 126
- Forks
- 60
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 5
Description
Environment
- OS: Windows 11
- Eclipse Version: 4.40
- Plugin Version: 0.20.0.202607100822 and also 0.21.0.202608060743
Describe the bug
UI Freeze when starting the Eclipse IDE.
My assumption is that the method com.microsoft.copilot.eclipse.ui.preferences.LanguageServerSettingManager.updateMcpToolsStatus () goes through all the projects in the workspace and it does so in the UI thread.
Pay attention to the Hits column on the right: the actual numbers are not real but the fact that there is a steep increase from 1 to 40+ shows that there is a for-loop somewhere that creates this issue. My bet is on the method com.microsoft.copilot.eclipse.core.utils.WorkspaceUtils.listTopLevelProjects ().
To Reproduce
Open the Eclipse IDE
Expected behavior
The UI shouldn't freeze, it should remain responsive
Additional context
We downgraded to version 0.19.0.202606240339 and we hope that this version doesn't have the issue. I will report back in this issue if 0.19.x also has this problem.
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 tracing com.microsoft.copilot.eclipse.ui.preferences.LanguageServerSettingManager.updateMcpToolsStatus() and com.microsoft.copilot.eclipse.core.utils.WorkspaceUtils.listTopLevelProjects(), focusing on whether workspace traversal runs on the UI thread. Reproduce by opening Eclipse with the reported plugin versions and confirm that startup remains responsive without the observed freeze.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100