Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Discussion options

Select Topic Area

Bug

Body

I am using the latest version of the Copilot IntelliJ plugin in CachyOS and the CPU usage quickly goes to 100% and never goes down. I tried with IntelliJ 2025.1 Beta, IntelliJ 2024.3 and IntelliJ 2024.2 and the results are similar. Sometimes CPU usage goes to 100% as soon as I open IntelliJ, and sometimes after I have used it for a few minutes. See images below.
CPU Usage

CPU usage extended

I am happy to provide any other information if that helps.

You must be logged in to vote

Replies: 16 comments · 12 replies

Comment options

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

  • Your input will be carefully reviewed and cataloged by members of our product teams. 
    • Due to the high volume of submissions, we may not always be able to provide individual responses.
    • Rest assured, your feedback will help chart our course for product improvements.
  • Other users may engage with your post, sharing their own perspectives or experiences. 
  • GitHub staff may reach out for further clarification or insight. 
    • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

  • Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
  • Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

  • Upvote and comment on other user feedback Discussions that resonate with you.
  • Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

You must be logged in to vote
2 replies
@louispool
Comment options

I understand that not all issues can be immediately investigated by the product team, but it's been nigh on 5 months without any response. This is a very real and problematic issue for a lot of people, this chat window occupies all 20 cores of my workstation and frequently causes all my peripherals to lock up.

@rumata28
Comment options

yeah, i also observer this. it looks like they are used my hardware to mine some coins...

Comment options

I've been experiencing the same for ~8 months. The 2 ways to circumvent this I found so far are:

  • Close and reopen the panel (it helps to map the action Open GitHub Copilot Chat to a key/shortcut):
  • Delete the current conversation.

In case it matters, I'm working on a TS project using IntelliJ Ultimate (Build #IU-243.26053.27, built on March 16, 2025) on a Mac M2. I had the same with all versions of intellij ultimate + copilot plugin in the last few months.

You must be logged in to vote
4 replies
@rumata28
Comment options

any news? that's frustrating... it looks like any JetBrains IDE suffers from this . I see this in WebStorm... Windows / Ubuntu - does not matter.

@ghillert
Comment options

This issue seems to be caused/triggered by the size of your AI Agent session. I accumulated a fairly large AI context and never bothered to create a new Agent Session. Once I did (Press New Agent Session), the CPU load went back to normal.

@conor888
Comment options

This issue seems to be caused/triggered by the size of your AI Agent session. I accumulated a fairly large AI context and never bothered to create a new Agent Session. Once I did (Press New Agent Session), the CPU load went back to normal.

Incorrect, can happen on new small chat sessions with code blocks in the history.

@ghillert
Comment options

@conor888 My apologies. Your are right. Just learned this the hard as my mac got uncomfortably hot. However, initially, at least right after clicking New Agent Session the CPU load does go down. But it looks like as soon as you add anything to the context or after a some period of time, the toaster is switched on. Bizarre that this is not treated as a blocker.

Comment options

any fix?

You must be logged in to vote
0 replies
Comment options

I experience this behavior as well. How can a chat window in IntelliJ take so many resources?
I'm using an M1 Pro 32GB on MacOS 15.6. 100% CPU usage when chat tool window is open, down to under 5% when chat window hidden.
IntelliJ version 2025.2, CoPilot Plugin version 1.5.53-243.

You must be logged in to vote
0 replies
Comment options

Also experiencing this. Up to date with the latest versions of Copilot and IntelliJ. Who should I send the invoice to for the extra power consumption I'm incurring?

You must be logged in to vote
0 replies
Comment options

Possible Causes & Fixes for 100% CPU in Copilot IntelliJ Plugin

I’ve seen similar high CPU issues with the Copilot IntelliJ plugin. Here are some things that usually help:

Update Copilot & IntelliJ

Make sure you’re running the latest versions of both IntelliJ and the Copilot plugin.

Older versions (esp. 2024.x builds) had memory leaks and indexing issues. Updating often fixes CPU spikes.

Disable Background Indexing / Plugins

Go to Settings > Plugins and temporarily disable heavy plugins (e.g., Lombok, SonarLint, etc.).

Some plugins clash with Copilot’s real-time code suggestion process.

Limit Copilot’s Context Window

In Settings > GitHub Copilot, reduce the context length or disable inline suggestions in very large projects.

Copilot tries to parse huge files and can hog CPU.

Check for Known Bug Reports

GitHub Copilot IntelliJ Issues
→ Many users reported similar 100% CPU issues, especially on Linux/CachyOS. Some fixes are already merged for upcoming releases.

Example issue: “Copilot plugin CPU usage spike on project load”.

Workaround Until Fix

Disable Copilot temporarily (Ctrl+Shift+A → Copilot: Disable) when you don’t need suggestions.

Restarting IntelliJ clears runaway Copilot threads if CPU stays locked.

Provide Logs to GitHub

Go to Help > Collect Logs and Diagnostic Data and attach them when reporting. It helps maintainers reproduce and patch the bug faster.

You must be logged in to vote
0 replies
Comment options

Experiencing this as well.

With copilot panel closed:
image

With copilot panel open:
image

You must be logged in to vote
1 reply
@palmerbl
Comment options

Same for me - High CPU usage when opening the GitHub Copilot "Chat" window only.

Inline suggestions works fine without much issue, everything at latest versions.

Comment options

I'm having the same problem under MacOS latest version (MBA apple silicon M3) , phpStorm 2025.2 and copilot updated.
In fact in Webstorm, PhpStorm, IntelliJ ....and so on...
Computer getting too hot.

If I open the copilot panel cpu goes crazy..

With copilot panel closed
27 08 2025-12 22 40

With copilot panel open
27 08 2025-12 23 11

You must be logged in to vote
0 replies
Comment options

The same problem occurs: if the Copilot window is open, WebStorm starts consuming 100% of the CPU.
WebStorm 2025.2 + copilot plugin.

You must be logged in to vote
0 replies
Comment options

Same situation here (PhpStorm 2025.2.1) when I open Copilot Chat, CPU usage goes to 100%.
Current work around that helps, but is very annoying to use, is to enable "power save mode" and then open the Copilot Chat. Looks like PhpStorm is trying to analyse the code suggestions in the Copilot Chat.

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@ClemMLD
Comment options

We absolutely need a fix for this, it's been going on for months.

Comment options

Seeing this now too on WebStorm 2025.2 with Copilot plugin 1.5.55-243, using 500% CPU with the GitHub Copilot panel open, goes back down to 5% CPU as soon as I close the panel

You must be logged in to vote
1 reply
@Zirkus-99
Comment options

I experienced the same issue. However, after reinstalling the IDE, the CPU usage dropped from over 500% to around 40% max when using the Copilot Chat window. Hopefully this information is helpful.

Comment options

You must be logged in to vote
1 reply
@admirlju
Comment options

No, it didn't. I've updated both PhpStorm (the issue is happening across all JetBrains IDEs) and the Copilot plugin. And the problem is still happening. From my testing, it's something related to the IDE and not the plugin, since if I go into power saving mode, it works fine; it's just very annoying to switch power saving on and off all the time.

Comment options

My phpstorm was on 900%+ cpu usage on my m4 macbook whenever I had github copilot chat window opened. This issue seems to be on version 2025.2.1. I downgraded to my phpstorm to version 2025.1.5.1 and it works completely fine and my phpstorm is on 30-40% cpu usage.

So to fix this is to just downgrade to version 2025.1.5.1

You must be logged in to vote
2 replies
@rumata28
Comment options

I logged an issue: https://intellij-support.jetbrains.com/hc/en-us/requests/8022397?page=1
JetBrains do not want to bother - they are saying that it is problem with plugin (who would doubt they would say that).

I found that minimizing CoPilot window lets CPU cool down. Even if in the background there is an ongoing conversation.

Would you please vote up this one:

@martinprucha
Comment options

At first I observed the same behavior when minimizing the window / hiding the plugin panel - when it lost focus the CPU usage dropped.

What did resolve the situation for me now was the deletion of conversation history.

I noticed then that when in Ask mode and the plugins response contained some formatted code snippet, the CPU usage immediatelly jumped up and it stayed that way whenever I returned back to plugin panel / window.

Comment options

You must be logged in to vote
0 replies
Comment options

Same issue

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended Copilot Code accurately and faster with your AI powered pair-programmer.
Morty Proxy This is a proxified and sanitized view of the page, visit original site.