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.
Build: NetBeans IDE 8.0.2 (Build 201411181905) VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18 OS: Mac OS X User Comments: gteichrow: WTF? lol Deadlock? GUEST: Switched to the console and ran a Maven build. Switching back to the IDE, the deadlock occured. GUEST: Not drop, just wtite something about IDE problem and i cant do anything. GUEST: Don't know. gteichrow: No idea... GUEST: ????????? ????????? ? ???????????????? ? ???????? ????????????? IDE. ????????? ?? ???????????, ???????? ???????????? ??????????????? ????????? ?????????. Stacktrace: org.netbeans.modules.deadlock.detector.Detector$DeadlockDetectedException: Thread-17 at sun.nio.fs.PollingWatchService$PollingWatchKey.cancel(PollingWatchService.java:308) at sun.nio.fs.PollingWatchService$PollingWatchKey.poll(PollingWatchService.java:331) at sun.nio.fs.PollingWatchService$PollingWatchKey$1.run(PollingWatchService.java:290) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
Created attachment 153645 [details] stacktrace
Please check the thread dumps attached. They seem to point to masterfs.
> Please check the thread dumps attached. They seem to point to masterfs. Sure. Thank you, David. The deadlock occurred on Macs that failed to initialize native FS notifier and used NIO2 notifier instead, and on BSDs that can use only NIO2 notifier. This is a duplicate of bug 246893, which was reported from OS Solaris. Thank you for reporting. *** This bug has been marked as a duplicate of bug 246893 ***