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.
This exception was fired randomly while clicking in the editor, several hours after starting NetBeans - what on earth is MenuWarmUpTask doing running at this point? java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:429) at org.openide.util.Mutex$QueueCell.sleep(Mutex.java:1388) at org.openide.util.Mutex.enter(Mutex.java:608) at org.openide.util.Mutex.writeEnter(Mutex.java:483) at org.openide.util.Mutex.access$100(Mutex.java:78) at org.openide.util.Mutex$Privileged.enterWriteAccess(Mutex.java:1438) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.refresh(FolderObj.java:226) at org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.refreshAll(FileObjectFactory.jav a:131) at org.netbeans.modules.masterfs.filebasedfs.FileBasedFileSystem.refresh(FileBasedFileSystem.java:120) at org.netbeans.modules.masterfs.MasterFileSystem.refresh(MasterFileSystem.java:199) at org.netbeans.core.ui.warmup.MenuWarmUpTask$NbWindowsAdapter.run(MenuWarmUpTask.java:131) at org.openide.util.Task.run(Task.java:207) at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:435) [catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:836)
Ups, I thin kwe have to find the reason why it still running ....
Strange. MasterFS involved?
MenuWarmUpTask is just abused to perform work done when app gets again focus that was lost. The work involves refreshing of FOs. Anyway I do not have clue what's wrong here.
I think that from Radim's explanation is obvious why MenUWarUpTask is involved in attached stacktrace. No idea why InterruptedException is thrown, definitely nothing to do with any FS impl. Radim mentioned that he is aware of some problems in RP that might cause throwing InterruptedException. Radim, please reasssing this issue appropriately or close it. I have no idea how to solve this issue.
Reassigning to Jarda. This bug is from June when he made changes to RequestProcesses that resulted to problems like this. So this is most likely duplicate of some already fixed bug.
*** This issue has been marked as a duplicate of 59904 ***
verified duplicate