[ https://issues.apache.org/jira/browse/NETBEANS-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gili updated NETBEANS-238: -------------------------- Attachment: code-complete-profiler.npss [~GeertjanWielenga] I was going to say that I remember seeing this problem on 8.2 final but then I ran across https://netbeans.org/bugzilla/show_bug.cgi?id=270632 Sure enough (I just checked) the problem does *not* occur in 8.2 final but did occur as far back as dev build 201705080001 (7 months after 8.2 was released). Notice that this bug report contains a profiler snapshot. It's not clear whether any committer ended up looking at it. So good news: this is a regression so it should be fixable. I also don't believe the problem is in Maven's end (because it is a regression, and because of what I'm about to share below). It should be possible to undo the damage, once we figure out what changed. I am attaching an updated IDE profiler dump for your review. This was collected using Apache Netbeans build 152. It shows that the Editor parser waits 7 seconds to acquire a lock. The culprit seems to be a Thread called {{Inactive RequestProcessor thread \[Was:Flush UI Logs/org.netbeans.modules.uihandler.UIHandler$2WriteOut]}} that spends 5 seconds invoking {{File.list()}} which invokes a Win32-specific implementation. It's not clear to me what files it is listing and whether this problem really is Win32-specific. I'm going to need help from one of the committers to proceed further (either reproduce the problem on your end, under Windows, or give me ideas of what to try next). Thank you. > Invoking code-complete in Maven projects is extremely slow > ---------------------------------------------------------- > > Key: NETBEANS-238 > URL: https://issues.apache.org/jira/browse/NETBEANS-238 > Project: NetBeans > Issue Type: Bug > Components: java - Editor > Affects Versions: 9.0 > Environment: build 152 > Reporter: Gili > Priority: Critical > Attachments: SlowCodeCompleteAntAndMaven.zip, > code-complete-profiler.npss > > > Say I'm in a class that has a field {{singletonScope}} where this class is > defined within the same Maven module. > I type {{singletonScope.}} then wait for auto-complete to suggest possible > methods. Code-complete takes roughly 10 seconds to come back. > This is reproducible 100% of the time. > Expected behavior: Code-complete should complete within 300ms or less. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org For additional commands, e-mail: commits-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists