This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 185076 - [69cat] Go to source delayed by another task
Summary: [69cat] Go to source delayed by another task
Status: RESOLVED DUPLICATE of bug 185004
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 normal (vote)
Assignee: Jan Lahoda
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-27 10:44 UTC by aldobrucale
Modified: 2012-05-29 08:09 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
profiler snapshot (27.42 KB, application/octet-stream)
2010-04-27 10:45 UTC, aldobrucale 		Details
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 aldobrucale 2010-04-27 10:44:51 UTC 
[ JDK VERSION : 1.6.* ]

In a bean declaration of a spring framework xml file  like this

<bean class="an.ExampleClass">
   ...
</bean>

ctrl-clicking on "an.ExampleClass" the wait icon is shown first, then after a
few seconds a dialog is shown saying "Lengthy operaton in progress" -
"Calculating declaration position". As soon as I hit the "cancel" button,
ExampleClass.java opens in the editor.
Comment 1 aldobrucale 2010-04-27 10:45:54 UTC 
Created attachment 98114 [details]
profiler snapshot
Comment 2 David Strupl 2010-09-21 11:29:42 UTC 
Passing to XML for evaluation.
Comment 3 Svata Dedic 2011-11-11 20:40:30 UTC 
31 kms spent in 
org.netbeans.modules.maven.hints.pom.StatusProvider$StatusProviderImpl.checkHints()
it seems that Nexus indexer is reading from the Net and blocking the parsing thread.

moving to Maven
Comment 4 Jesse Glick 2011-11-16 01:00:20 UTC 
I do not see the Maven code doing anything wrong here. It is running a POM-related hint, which needs the repository index, in its own request processor thread. If something else is waiting for this, it is not apparent from the profiler snapshot.
Comment 5 Miloslav Metelka 2012-05-29 07:40:17 UTC 
Honzla L. will take care of this (moving to java/source).
Comment 6 Jan Lahoda 2012-05-29 08:09:02 UTC 
Dupe of bug #185004, to the best of my knowledge.

The problem is that ElementOpen was called under the Java lock, and forked a new thread, waiting for its completion, and this new thread wants to get the Java lock as well. Which obviously led to a deadlock. Canceling the UI part of the deadlock unlocked the Java lock, allowing the background thread to proceed.

*** This bug has been marked as a duplicate of bug 185004 ***