Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 332427 - Race condition in EclipseApplicationLaunchConfiguration.preLaunchCheck
Summary: Race condition in EclipseApplicationLaunchConfiguration.preLaunchCheck
Status: CLOSED WONTFIX
Alias: None
Product: PDE
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: PDE-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-13 06:45 EST by Markus Keller CLA
Modified: 2019-09-09 02:20 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2010-12-13 06:45:00 EST 
N20101212-2000

I launched the same Eclipse Application launch configuration twice while a build was still going on. After build was done, both launches started an then stalled in a livelock at 57%. All the other threads were idle, but two workers looped in HashMap.put(..). Cancel in the Progress view didn't work, had to kill the threads.


"Worker-44" prio=6 tid=0x3a4d6c00 nid=0x1d74 runnable [0x3d02f000]
   java.lang.Thread.State: RUNNABLE
        at java.util.HashMap.put(HashMap.java:374)
        at org.eclipse.pde.launching.EclipseApplicationLaunchConfiguration.preLaunchCheck(EclipseApplicationLaunchConfiguration.java:255)
        at org.eclipse.pde.launching.AbstractPDELaunchConfiguration.launch(AbstractPDELaunchConfiguration.java:61)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
        at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:925)
        at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1129)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


"Worker-27" prio=6 tid=0x3a4d9c00 nid=0x1940 runnable [0x3947f000]
   java.lang.Thread.State: RUNNABLE
        at java.util.HashMap.put(HashMap.java:374)
        at org.eclipse.pde.launching.EclipseApplicationLaunchConfiguration.preLaunchCheck(EclipseApplicationLaunchConfiguration.java:255)
        at org.eclipse.pde.launching.AbstractPDELaunchConfiguration.launch(AbstractPDELaunchConfiguration.java:61)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
        at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
        at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:925)
        at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1129)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:08:10 EDT 
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 2 Julian Honnen CLA 2019-09-09 02:20:16 EDT 
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.