| Summary: | deadlock detected in org.eclipse.jdt.launching | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Kevin Tapperson <kevintap> |
| Component: | Debug | Assignee: | JDT-Debug-Inbox <jdt-debug-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | sarika.sinha |
| Version: | 4.4.2 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | stalebug | ||
|
Description
Kevin Tapperson
Do you have some reproducible scenario so that we can work on it? As I don't have the scenario, going through the code it is a possibility that org.eclipse.jdt.internal.launching.LaunchingPlugin.restoreLibraryInfo() is causing a locked state. 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. |