[
https://issues.apache.org/jira/browse/NETBEANS-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905420#comment-16905420
]
Laszlo Kishalmi commented on NETBEANS-2940:
-------------------------------------------
Well, thank you for the profiler snapshots. What is strange that in is the
FileOwnerQuery what is responsible almost the ~45% of the CPU usage in the
latest snapshots.
That query shall be much lighter It seems that the Archive file handling part
is heavy there, maybe we can do some improvements there. I guess not all
parsers utilize this query equally, so it's slowness might hurt the JS indexing
performance.
!image-2019-08-12-10-34-22-305.png!
> StackOverflow on JavaScript Indexing
> ------------------------------------
>
> Key: NETBEANS-2940
> URL: https://issues.apache.org/jira/browse/NETBEANS-2940
> Project: NetBeans
> Issue Type: Bug
> Components: javascript - Editor
> Affects Versions: 10.0, 11.1
> Reporter: E Dementiev
> Priority: Major
> Attachments: 2019-08-08-08-00-01.png, 2019-08-08-12-00-01.png,
> 2019-08-08-14-00-01.png, 2019-08-09-09-00-01.png,
> 2019-08-09-09-00-02-htop.png, 2019-08-09-09-00-03.png,
> 2019-08-09-09-00-05.png, 2019-08-09-09-00-exception-log.txt,
> 2019-08-09-12-00-01-JRE.png, 2019-08-09-14-00-01.png,
> 2019-08-09-14-00-02.png, 2019-08-09-14-00-02.png, 2019-08-09-14-00-03.png,
> 2019-08-09-14-00-03.png, 2019-08-09-17-30-IDE-log.txt,
> 2019-08-09-17-30-java.lang.StackOverflowError.txt,
> 2019-08-09-netbeans-11.1-about.png, 2019-08-09-netbeans-8.2-about.png,
> image-2019-08-12-10-34-22-305.png, netbeans-11.1.conf, netbeans-8.2.conf,
> selfsampler15073537369378979592.npss, selfsampler17323576831159964034.npss,
> selfsampler1962235903870517275.npss, selfsampler231953002133054481.npss,
> selfsampler4257377310219144311.npss, selfsampler4496583350478949316.npss
>
>
> Very often Netbeans would start consuming high CPU resources for the job of
> Checking for external changes, which sits in suspended status. If you click
> on the cross and manually cancel that job, the CPU will keep being consumed.
> The only way to stop this is to completely close Netbeans. Upon closing, it
> will say that it is still checking for external changes.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
