I’ve found that 2026.1 seems to be having some issues with how the JVM is using memory. Here’s a key example:
Note that the IDE is configured is follows:
IntelliJ IDEA 2026.1.3
Build #IU-261.25134.95, built on June 3, 2026
...
Memory: 4096M
It’s very possible that the 257MB value was after a forced GC, but obviously it was no more than 1600MB out of the 4GB I’ve allocated to the process. And this is on a machine with 32GB of physical memory with plenty of breathing room when this happened.
Should I report this as a bug in YT?
Between this is the increasingly frequent “IntelliJ IDEA is not responding … Dump threads” messages I see during normal Java dev on my plugin, 2026.1 is feeling really sketchy to me.
Do you have logs? May be freeze dumps from directory may reveal the cause
For this memory issue, no. Just the screenshot. For the “not responding” issues, I’ve grabbed several, and they’re all over the place, but always in core IDE functionality. I’ve disabled all first-/third-party plugins that aren’t strictly needed for my plugin dev tasks to rule those out, but it still happens roughly dozens of times every day.
I’ll try to grab thread dumps from any that happen today – if the pauses are long enough for me to react to them – and provide them.
Regarding “IntelliJ IDEA is not responding … Dump threads” messages, we can disable these messages (and the dump threads): https://youtrack.jetbrains.com/issue/IJPL-245937
I did this, at least on my dev machine because my CPU is simply too weak for my workload ^_^.
What kind of workload is that? Are you sure those are not simply real bugs/freezes?
@illuminatedcloud in such problems CPU snapshots are really useful, because they record mem allocations also in JFR. Help - Start CPU Usage Profiling
@jonathanlermitage.1, thank for sharing. Obviously that’s a sort of workaround and not a solution because the freeze is still going to happen, but at least it’s not quite as in-your-face. I’ll leave them enabled for a bit to see if I can get thread dumps that I can share with JetBrains in hopes of fixing the core issues.
To be 100% candid, though, something has changed in the last few IDE releases. And it’s not just me noticing it, but I’m hearing about it from users of my commercial plugin. I’m getting concerned about overall customer satisfaction for something that’s not entirely under my control. Don’t get me wrong…I always start by assuming that I need to address things – and there have been plenty of things identified by these diagnostics that I’ve needed to address for sure – but users are reporting more frequent and long-running indexing/analyzing, freezes, workflow-interrupting messages like these “not responding” ones, etc.
Not trying to dump here because, as I said, this has kicked over plenty of things that I’ve needed to address in my own plugin, but given that I experience the same things when working in a pretty stock-standard IntelliJ IDEA install for plugin dev, it raises (IMO legitimate) concern about perceived quality of the overall solution. So I’d like to help contribute any diagnostics that can help with the things that aren’t under my direct control.
Also, the “Dump threads” feature doesn’t work reliably, specifically for these instances that are so short-lived as to be imperceptible by the end user if not presented with the “not responding” modal. I just had one that lasted about a second or two, and when I hit CTRL+D, it opened an empty thread dump folder:
So basically all of the downsides of this “feature” with none of the benefits.
No, it happened frequently when starting an IDE (or, worse, the JetBrains Client + an IDE backend on the the machine), with and without 3rd-party plugins, on a Linux VM (currently EndeavourOS, but I spent a lot of time testing various distros).
Everything is slower in VirtualBox or VMware, even when configured correctly, and my Intel i7 8750H is a bit outdated.
@Scott Wells yeah, I agree. I use this workaround because, on my machine, these warnings are like false positives. My machine is just too weak, and my IDEs (in VMs) are a bit slow to start, but I’m okay with that.
Your issue is different, and more serious.
