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 252619 - 189,567 instances of org.netbeans.modules.masterfs.filebasedfs.naming.FileName
Summary: 189,567 instances of org.netbeans.modules.masterfs.filebasedfs.naming.FileName
Status: RESOLVED INCOMPLETE
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 8.1
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-27 13:48 UTC by terje7601
Modified: 2016-08-05 08:32 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (495.05 KB, application/octet-stream)
2015-05-27 13:48 UTC, terje7601 		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 terje7601 2015-05-27 13:48:29 UTC 
Created attachment 153903 [details]
IDE log

I had ~10 projects open, some Maven-based Java EE Web projects, the others being HTML5 projects.
Comment 1 terje7601 2015-05-27 14:03:16 UTC 
The heap dump was uploaded in builds #660 and/or #661 (both the Parameters & the Console Output are the same, so I don't know where the difference is).
Comment 2 terje7601 2015-05-28 08:06:02 UTC 
For completeness, my environment is:

Product Version: NetBeans IDE Dev (Build 201504230001)
Updates: Updates available
Java: 1.8.0_45; Java HotSpot(TM) 64-Bit Server VM 25.45-b02
Runtime: Java(TM) SE Runtime Environment 1.8.0_45-b14
System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
Comment 3 Tomas Hurka 2015-05-28 11:37:02 UTC 
Thanks for the heap dump. It was uploaded twice, uploaded files are identical.
Comment 4 Tomas Hurka 2015-05-29 08:06:58 UTC 
There are 189,567 instances of org.netbeans.modules.masterfs.filebasedfs.naming.FileName. It looks like most of the instances come from registered deep filesystem listeners (RepositoryUpdater$FCL).
Comment 5 terje7601 2015-05-29 09:23:48 UTC 
Yes. Our setup is like this:
we have one separate HTML5 project per "module", and then one "application" project which contains links (in this case: directory junctions) to all the other projects. So we have:

application
-- node_modules
-- module1
----- node_modules
-- module2
----- node_modules
-- module3
----- node_modules
...

For the application we use npm to run a simple web server which serves all modules.

For the modules, we use npm only to build each module with grunt (& thus the node_modules is mostly identical across modules). So NetBeans can just ignore those directories, because they are only used indirectly through grunt invocations.

I already reported a related issue about opening of projects being very slow ( https://netbeans.org/bugzilla/show_bug.cgi?id=249908 ). This was also due to listening on the full node_modules subtrees. That issue was resolved, but it seems there are still other problems with this, such as this one.
Comment 6 Tomas Hurka 2016-08-05 08:32:15 UTC 
Can you, please, test your scenario in current NetBeans dev. build? Does it work fine?