Patrick Ziegler

Apologies for the late response. I really like just how much cleaner this looks now, so no objections from my side, either.

As far as I understand the initial bug, the issue was reported for the Java editor. My proposal is to push this restriction to the [JavaSourceViewerConfiguration](https://github.com/eclipse-jdt/eclipse.jdt.ui/blob/master/org.eclipse.jdt.ui/ui/org/eclipse/jdt/ui/text/JavaSourceViewerConfiguration.java) by subclassing the ContentAssistant...

I don't think it's worth the trouble trying to fix this across different projects, so we'll just continue with the workaround. The fix is in the linked PRs and 100%...

Perhaps I'm missing something here, but where exactly is the wizard opened? The progress dialog remains open until `IRunnableWithProgress` completes. So I assume the wizard is opened there? How do...

This side is looking good. But until I get a response from the JDT team, this is effectively blocked unless I want to reintroduce the original bug.

> I'm tring to avoid lock of eclipse 2025-03 in a normal search java file \r\n and substitute with ")\r\n or searching in any project of workspace a string. >...

If you use e.g. VisualVM, you should be able to create a heap dump. That should already give an indication of which components keep all that memory locked. You can...

> It's possible to reproduce in 2025-06 M3 if you perform the same expensive search twice. > > The 1st time, the UI became unresponsive for "only" 5-10 seconds but...

Whatever is causing this has to be very likely be on the EGit side, not the SWT side. Specifically something introduced with 7.4. This is the 2025-06 with EGit 7.3,...

Not in the video, but using the 2025-12 M2 with EGit 7.3 also behaves as it should. If you look closely at the recording, you'll notices that the staging view...