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 36787 - Double clicking '.java' file in Windows Explorer deadlocks IDE.
Summary: Double clicking '.java' file in Windows Explorer deadlocks IDE.
Status: VERIFIED DUPLICATE of bug 34943
Alias: None
Product: platform
Classification: Unclassified
Component: Text (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Petr Nejedly
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2003-10-23 11:35 UTC by simongreenaway
Modified: 2008-12-22 23:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thread dump (10.81 KB, text/plain)
2003-10-23 11:36 UTC, simongreenaway
Details

Note You need to log in before you can comment on or make changes to this bug.
Description simongreenaway 2003-10-23 11:35:27 UTC
1. Double click on an external .java file in
Windows Explorer.
2. Click on netBeans *quickly*.
3. Hangs with the java editor showing "1: " (line
numbering is switched on).

This is an intermittant fault, I cannot resolve
which part of the IDE I am clicking on to
reproduce the fault, it just happens about 1 in 10
times.

Note this occurs on version 3.5 and 3.5.1

Simon Greenaway
Comment 1 simongreenaway 2003-10-23 11:36:08 UTC
Created attachment 11947 [details]
Thread dump
Comment 2 simongreenaway 2003-10-23 12:21:05 UTC
The clicking on the IDE to regain focus after the double-click in
Windows   Explorer is not relevant - it just deadlocked without having
the focus!
Comment 3 Miloslav Metelka 2003-10-24 16:43:11 UTC
Reassigning to openide/editor.
Syncing RP is loading a doc but waits on "lines" while AWT holds
"lines" but waits on doc loading.

This problem exists in 3.5 and 3.5.1 and it will probably occur even
with the current openide.text in the trunk. The recent patch that I've
did will not solve this sort of problem.

There might be a solution to sync on CloneableEditorSupport.getLock()
instead of "lines" var in all the occurrences. As the
CES.openDocument() waits on CES.getLock() (i.e. it releases the lock)
the RP could proceed. But it's just an idea that would have to be tested.
Comment 4 Petr Nejedly 2003-11-27 09:25:54 UTC
Different way to reach the same deadlock as issue 34943.

*** This issue has been marked as a duplicate of 34943 ***
Comment 5 Marian Mirilovic 2004-02-29 09:22:09 UTC
verified diplicate