Community
Participate
Working Groups
Here is the race report given by a dynamic race detector: Data race on field org.eclipse.debug.internal.core.InputStreamMonitor.fThread: {{{ Concurrent write in thread T39 (locks held: {}) ----> at org.eclipse.debug.internal.core.InputStreamMonitor.close(InputStreamMonitor.java:115) at org.eclipse.debug.internal.core.StreamsProxy.close(StreamsProxy.java:72) at org.eclipse.debug.core.model.RuntimeProcess.terminated(RuntimeProcess.java:238) at org.eclipse.debug.core.model.RuntimeProcess$ProcessMonitorThread.run(RuntimeProcess.java:434) T39 is created by T1 at org.eclipse.debug.core.model.RuntimeProcess.<init>(RuntimeProcess.java:125) Concurrent read in thread T38 (locks held: {}) ----> at org.eclipse.debug.internal.core.InputStreamMonitor.write(InputStreamMonitor.java:124) at org.eclipse.debug.internal.core.InputStreamMonitor$1.run(InputStreamMonitor.java:100) T38 is created by T1 at org.eclipse.debug.internal.core.InputStreamMonitor.startMonitoring(InputStreamMonitor.java:104) }}}
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
@Paul, Can you check if it was resolved through some of your bug?
No. I think the problem persists.
