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 179544 - Deadlock while renaming a JavaFX file
Summary: Deadlock while renaming a JavaFX file
Status: RESOLVED DUPLICATE of bug 179446
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Mercurial (show other bugs)
Version: 6.x
Hardware: PC Linux
: P1 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-15 06:42 UTC by Petr Nejedly
Modified: 2010-01-26 02:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
The thread dump. (18.10 KB, text/plain)
2010-01-15 06:42 UTC, Petr Nejedly 		Details
IDE log from the deadlocked session (131.93 KB, text/plain)
2010-01-15 06:46 UTC, Petr Nejedly 		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 Petr Nejedly 2010-01-15 06:42:32 UTC 
Created attachment 93317 [details]
The thread dump.

Copy a (fx) file into the same package, you'll get file_1.fx.
Click on it in the explorer and in-place rename it to file2.fx.
The IDE will deadlock in mercurial integration, after issuing a warning that an external command is executed in AWT.
Comment 1 Petr Nejedly 2010-01-15 06:46:15 UTC 
Created attachment 93318 [details]
IDE log from the deadlocked session

Added the IDE log. I originally thought this is a Mercurial issue, but the problem doesn't happen when renaming a java file in the same context.
I don't see much difference in the implementation of JavaNode/DataObject and their JavaFX counterparts though.
Comment 2 Adam Sotona 2010-01-26 01:54:46 UTC 
For me it looks like deadlock within the Mercurial support.
I don't see any part where I can help from JavaFX codebase.
Comment 3 Ondrej Vrabec 2010-01-26 02:00:35 UTC 

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