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 61652 - What is the MenuWarmUpTask doing in Refresh-After-WindowActivates thread ?
Summary: What is the MenuWarmUpTask doing in Refresh-After-WindowActivates thread ?
Status: CLOSED WONTFIX
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 5.x
Hardware: All All
: P1 blocker (vote)
Assignee: rmatous
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2005-08-02 12:42 UTC by Marian Mirilovic
Modified: 2008-12-22 15:48 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Marian Mirilovic 2005-08-02 12:42:02 UTC 
NB.dev(200508011800), JDK 6.0(b43)

When I come back to IDE , the IDE is slipping and in the thread-dump I found
next lines:

"Refresh-After-WindowActivated" daemon prio=1 tid=0x4d247a00 nid=0x151f runnable
[0x4cccc000..0x4cccc5d8]
   java.lang.Thread.State: RUNNABLE
        at java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
        at java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:228)
        at java.io.File.exists(File.java:725)
        at
org.netbeans.modules.masterfs.filebasedfs.children.ChildrenSupport.getSubsetOfExisting(ChildrenSupport.java:252)
        at
org.netbeans.modules.masterfs.filebasedfs.children.ChildrenSupport.refresh(ChildrenSupport.java:217)
        at
org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj$FolderChildrenCache.refresh(FolderObj.java:399)
        at
org.netbeans.modules.masterfs.filebasedfs.fileobjects.FolderObj.refresh(FolderObj.java:229)
        at
org.netbeans.modules.masterfs.filebasedfs.fileobjects.FileObjectFactory.refreshAll(FileObjectFactory.java: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:469)
        at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:870)
Comment 1 rmatous 2005-08-29 10:00:51 UTC 
There is no specail code in MenuWarmUpTask. Just window activation listener is
registered. This code is there since 4.0. There were discussions where should it
be moved (there were no significant objections against MenuWarmUpTask).
Definitely moving registration from MenuWarmUpTask doensn't affect performance
in any way. There were already issues related to refreshing filesystem, there
were logging issues - investigated by Petr Nejedly => were closed finally.
Comment 2 Marian Mirilovic 2005-10-19 15:12:33 UTC 
v/c