[ 
https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16648731#comment-16648731
 ] 

Laszlo Kishalmi commented on NETBEANS-168:
------------------------------------------

Well I guess this can be caused by miss behaving plugins and maybe some edge 
cases.
I'm seeing something similar after waking up from sleep and editing the files. 
the IDE starts to eat 200%-300% CPU, though remain usable.

Though after a while (it can be even 30 minutes) the processor usage become 
normalized.
I was able to attach a profiler to the IDE while this was happening. It seems 
there is something fishy around the FileObjects and FileChange listeners.
The IDE was actually burning CPU onĀ  File.isFile and File.isDirectory methods. 
So plugins registering FileChangeListeners non-carefully could trigger this 
issu.

Though it might be something wrong on the FCL implementation. If my time allows 
I try to craft some monitoring around this.

> Background scanning process needs a rethink
> -------------------------------------------
>
>                 Key: NETBEANS-168
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-168
>             Project: NetBeans
>          Issue Type: Bug
>          Components: ide - Performance, java - Platform, platform - Execution
>    Affects Versions: 8.2, Next
>         Environment: NetBeans 8.2, Windows 10 x64
>            Reporter: Christian Lenz
>            Priority: Critical
>
> Often, while cloning, switching branch, merging, opening etc. etc. NetBeans 
> starts Background scanning for changes, but it is not real background, 
> because everything what you want to do then, like changing the branch, 
> commit, push, pull, open project, delete or whatever, is blocking by this 
> task and you can't cancel it, because it is essential.
> Either we need to rethink about this process like to make everything or most 
> of the stuff doing things in parallel or the task should really be 
> cancelable. It is a pain in the ass for big projects when they start to scan 
> for changes. 
> It is a real world case because you acan see it when you work on NetBeans 
> modules.
> Cheers
> Chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
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

Reply via email to