Laszlo Kishalmi commented on NETBEANS-168:

Well, the real issue is really hard to catch, not even debug that.

What happens with me is that sometimes the IDE starts to peg the CPU checking 
for external modifications. It is also can result heavy GC and sometimes a 
memory leak. I just don't know how to trigger that. But it happens with me 
almost daily. Most of the time the IDE is restored itself in 20-30 minutes of 
heavy disk and CPU work. As of the source scanning it is just really matter of 
milliseconds, seconds maybe.

> 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