[NETBEANS-168] Background scanning process needs a rethink

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Invalid
• Affects Version/s: 8.2, 9.0, 10.0
• Component/s: ide - Performance, java - Platform, platform - Execution
• Labels: ca_survey

Environment

NetBeans 8.2, Windows 10 x64

• Assignee: Unassigned
• Reporter: Christian Lenz
• Created: 25/Nov/17 19:47
• Updated: 03/Nov/20 15:50
• Resolved: 09/Mar/19 05:30

Description

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

Issue Links

• is related to: NETBEANS-2224 Add support for Broken Symlinks
• relates to: NETBEANS-2525 Background Scanning Process for first NetBeans start took more than 15min
• relates to: NETBEANS-1845 Burning CPU on broken Symlinks
• relates to: NETBEANS-1872 CSS parser loops infinitely with specific code
• relates to: NETBEANS-1929 Hangs during the "Background scanning the projects"
• mentioned in: Page Loading...