microsoft / microsoft/copilot-for-eclipse

Eclipse Code mining: Line jumping flickering with Copilot installed although completion is disabled

Open
#61 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
126
Forks
60
Avg merge
2d 6h
Merged PRs (30d)
5

Description

It seems Copilot plugin is causing a repaint on every key-stroke even though Copilot completions are turned of. This results in jumping lines / flickering when Code Mining (e.g. method references) are enabled.

See the following comment by me with a description and videos of the problem:

https://github.com/eclipse-platform/eclipse.platform.ui/issues/2786#issuecomment-3642875815

which I am quoting here.
Not sure this is known but I noticed it today in new Eclipse 2025-12. Maybe it has been there before in 2025-09 too, but I don't know.

... here is a video of my current Eclipse where I see the flickering / jumping.
Notice that where I type the numbers, every keypress causes re-rendering.

Image

https://github.com/user-attachments/assets/7853b764-bfc1-4336-976b-383e8ce88fcc

Environment

Eclipse IDE for Eclipse Committers (includes Incubating components)
Version: 2025-12 (4.38.0)
Build id: 20251204-0850

I have Copilot plugin installed (a suspicion, because on another 2025-12 instance, I don't have Copilot and I don't see this effect)

  • GitHub Copilot 0.13.1.202511180215 com.microsoft.copilot.eclipse.feature.feature.group GitHub Copilot

BUT copilot completions are currently disabled.

Uninstalling Copilot

For comparison here is the same Eclipse with Copilot uninstalled.

https://github.com/user-attachments/assets/f475f83d-c1dc-4db4-8206-8cf4abd7ae0a

So I guess it is Copilot.

But maybe it helps others or you could tell the Copilot team about this.

Update: What I can't remember is if how exactly it behaved with 2025-09. It was just today that I found it very annoying so that I took the effort to google for the problem and found this issue.

Originally posted by @chrisrueger in #2786

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the flickering in Eclipse 2025-12 with Code Mining enabled, comparing Copilot installed versus uninstalled and completions disabled. Review the linked Eclipse Platform UI issue #2786 and the Copilot plugin behavior; done means identifying and addressing the repaint cause, then confirming that line jumping no longer occurs under the reported conditions.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
desktop, developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.