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 271536 - Deadlock on Go To Source from a method call in the Debugging stacktrace topcomponent
Summary: Deadlock on Go To Source from a method call in the Debugging stacktrace topco...
Status: NEW
Alias: None
Product: editor
Classification: Unclassified
Component: Hints & Annotations (show other bugs)
Version: 8.2
Hardware: PC Other
: P3 normal with 3 votes (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-27 13:35 UTC by matteodg
Modified: 2017-09-27 13:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread dump when in deadlock (42.10 KB, application/octet-stream)
2017-09-27 13:35 UTC, matteodg
Details
Another thread dump (37.92 KB, application/octet-stream)
2017-09-27 13:43 UTC, matteodg
Details

Note You need to log in before you can comment on or make changes to this bug.
Description matteodg 2017-09-27 13:35:33 UTC
Created attachment 165189 [details]
Thread dump when in deadlock

In a NB platform application I have unit tests in a module, I was launching a "Debug File" action on a Test file.
Once hit a breakpoint I right-clicked on a method call in the stack trace in the Debugging top component and selected the "Go To Source" action.
Then I got the deadlock.

From the attached thread dump it seems a problem with annotations, but not sure.

This is the third time it happens, I'll attach thread dumps as the deadlock happens again.
Comment 1 matteodg 2017-09-27 13:43:37 UTC
Created attachment 165190 [details]
Another thread dump

This time I just opened a XXXXTest.java file, so it might be dependent on the content of the file.

I can send the file, but not here in the public