-
Notifications
You must be signed in to change notification settings - Fork 151
Description
Let's make sure issue is not already fixed in latest builds first.
- I verified I can reproduce this issue against latest Integration Build of Eclipse SDK
Steps to reproduce
From a fresh installation and clean workspace:
-
Install CDT (https://download.eclipse.org/tools/cdt/releases/12.4/cdt-12.4.0/ - just C/C++ Dev tools is enough:

-
Create a Classic C hello world project
-
Build and Debug
-
Quit Eclipse with debug session active
I get multiple entries in the debug log which are variants of this stack trace
!ENTRY org.eclipse.debug.core 4 125 2026-03-06 11:18:56.896
!MESSAGE An exception occurred while dispatching debug events.
!STACK 0
java.util.concurrent.RejectedExecutionException: org.eclipse.swt.SWTException
at org.eclipse.swt.widgets.Display.execute(Display.java:971)
at org.eclipse.debug.internal.ui.views.console.ProcessConsole.resetName(ProcessConsole.java:651)
at org.eclipse.debug.internal.ui.views.console.ProcessConsole.handleDebugEvents(ProcessConsole.java:639)
at org.eclipse.debug.core.DebugPlugin$EventNotifier.run(DebugPlugin.java:1422)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:47)
at org.eclipse.debug.core.DebugPlugin$EventNotifier.dispatch(DebugPlugin.java:1456)
at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:521)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
Caused by: org.eclipse.swt.SWTException
... 8 more
AFAICT this was introduced by the cleanups in ProcessConsole, specifically https://github.com/eclipse-platform/eclipse.platform/pull/2427/changes#diff-60fe71e794e66cadecbd8f6789de6d44c5f1b49e7fdebd919e42e7feb99a0846R651 where a UIJob was replaced with DebugUIPlugin.getStandardDisplay().execute
Note: I think this affects CDT and not a similar JDT setup because CDT's console doesn't have a timer in the console title.
Tested under this environment:
- OS & version: Linux Ubuntu 25.10 with KDE
- Eclipse IDE/Platform version (as shown in Help > About): 2025-12 R and retested on I20260305-1800
- ...Anything else that can be useful...
Community
- I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.