Laszlo Kishalmi commented on NETBEANS-168:

I fear we are talking about different issues. Today finally I got something out 
of profiler.

A File deleted event hit the fan, Which took 100% CPU on otherwise idle IDE.
As I'm developing NetBeans in NetBeans it seems the NetBeans Project UI Support 
gone wild, got responsible for 60% of CPU on:

Even if none of the important files node were open in the IDE (though I opened 
a few in my session). I guess we have listener leak here.

There is another candidate with 23% CPU time:


> 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
>         Attachments: messages 10.0 vc2.log, messages.log, ui.log, uigestures 
> 10.0 vc
> 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

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:

Reply via email to