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

Christian Lenz commented on NETBEANS-168:
-----------------------------------------

It is not blocking the IDE, but it is blocking the interaction. When you have 
multiple big projects and they need a background scan for whatever reasons, the 
other actions are in the queue like cloning, commit, pushing, pulling, etc. 
they will not doing stuff in parallel or the background action is blocking all 
of the other actions. When I did smth I don't know atm and I want to commit or 
push it NOW, the background scan is blocking the whole action. After sometimes 
30s or how long the background scanning process is running, it ends (sometimes, 
sometimes later) and the other actions in the queue can executed immediately. 
This behaviour is unacceptable. I can't do some actions until the background 
scanning ends.

> 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
(v6.4.14#64029)

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

Reply via email to