2025.2.3 some things are VERY slow
Hi all,
I just upgraded to 2025.2.3, and some operations are SUPER slow. Copying a single line of text to the clipboard pops up a window with a progress bar and can take several seconds to complete. Just now, the editor suggested a simplification to code that was about 20 characters long. It took 15 seconds. I'm on a Win 11 VM with an 8-core CPU (AMD Ryzen 9 7950X) and 32GB RAM, all 4th Gen m.2 drives, and nothing on this machine is slow! But after I upgraded to 2025.2.3 - Build #PS-252.26830.95, built on October 2, 2025, some simple operations are very slow.
Sometimes, copy to clipboard works normally, but sometimes, it pops up this window and takes 10-15 seconds to finish.
Any ideas?
Best regards,
Please sign in to leave a comment.
Same problem for me, it takes a very long time to copy lines of text, even from ai assistants window, or inside classes, it does not show everytime, it ‘fixes’ itself for a while and out of nowhere starts slowing again, no elevated cpu usage seen when it does that, very annoying.
I have a similar problem. When copying Java code from AI Chat or using "remove unused imports" in Java class, I get the process bar and hang for up to 10 seconds.. Intel ultra 220H processor and I had the same problem on Ryzen 7 5825U processor. Version ide 2025.2.3. Windows 11
Similar here, And it take 12 seconds also to right click on a folder to open the popup. Copy show a popup also, and sometime click on a word take seconds for “search of occurence”
Hi!
Since the root cause of each issue can be different, I ask you to submit separate requests to support via Help > Contact Support. Please describe the issue you’ve faced and share the logs from Help > Collect Logs and Diagnostic Data for further investigation. Thank you!
Hi,
I personnaly already did it a few days ago
for other people, If I disable the AI plugin it go fast again, And I think the bug start after claude agent installation in the official jetbrains AI plugin
Like Stanislas, I'm also using the Claude plug in and this also started after I installed that plugin, but I had also installed couple of PHPStorm upgrades at the same time, so didn't relate it to the AI plugin.
I will send in a report next time it happens :)
some more information : it seems to appear if I have the AI Chat open on a discussion, and disappear il I switch to a blank new chat.
Same issue with IDEA, simple copy operation now takes 10 - 15 seconds. Fairly reproducible from the AI assistant window. Less reproducible in the editor tabs. This affects all operations that touch the AI it seems. Renaming fields, anything that scans any kind of context. With AI Assistant plugin disabled it's smooth sailing.
What used to be instant now feels like turn-based strategy.
The issue with the AI Assistant is known and has already been fixed for the 2025.2.4 version of JetBrains IDEs: LLM-20308. Consider updating the IDE as soon as the new version is available.
AI is not performing well, and even the core IDE—which is your main product—is in such poor condition.
We are paying customers, yet this is the kind of experience we are getting. This really needs to be reviewed and taken seriously.
This has already become an incident that severely impacts our work. I urgently needed to work on code, and the IDE was completely unusable.
What exactly is going on?
Hello Linilnjohnny2,
Could you please provide more details? Let us know your IDE version and clarify what isn’t working as expected. If you are experiencing freezes, please mention when they occur, such as while typing, navigating menus, or performing Git operations, etc. Any related error messages or screenshots would also be helpful.
For further investigation, please also share your IDE logs by uploading them at https://uploads.jetbrains.com/ and provide the upload ID.
Anastasiia Zyrianova :
IDE freezes when using Git tool window (cherry-pick / view commit changes)
Environment
Description
PhpStorm frequently becomes completely unresponsive when using the Git tool window.
Issues
Notes
Expected vs Actual
Linilnjohnny2,
Please see IJPL-219220 for details and apply the workaround mentioned in this issue. It is specific to the 2025.3 version only.