[NETBEANS-5380] Background scanning spends significant time in o.n.m.j.mx.project.SuiteFileOwnerQueryImpl#getOwner

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Next
• Fix Version/s: 12.4
• Component/s: java - Source
• Labels: pull-request-available
• Assignee: Matthias Bläsing
• Reporter: Matthias Bläsing
• Created: 20/Feb/21 21:41
• Updated: 03/Mar/21 20:52
• Resolved: 03/Mar/21 20:52

Description

I opened an angular project into an IDE build from recent master. I observed, that a very (> 20 minutes) long background scanning times could be observed. I first used visual VM and then the netbeans internal profiler to try to narrow it down.

Profile

I'll attach two self profiles, both show the same picture, so I'll concentrate on sample2.npss:

There are 9 entries in the self profile, that show CPU times > 190s. From these 8 are waiting in native code and thus false positives:

• ReferenceHandler
• FileSystemWatchService
• process reaper (3x)
• StreamTerm.Output (2x)
• pool-5-thread-1 (From the trace LSP integration)

The one trace, that is connected to the observed scanning and is in java code is RepositoryUpdater.worker. Breaking this down shows, that, although the forward calls split into two branches, both hit:

org.netbeans.modules.java.mx.project.SuiteFileOwnerQueryImpl#getOwner

That method is responsible for 178s CPU time. No other FileOwnerQueryImpl shows up in the trace, and thus this leads me to the conclusion, that this is fishy.

 

Issue Links

• links to: GitHub Pull Request #2789