You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@netbeans.apache.org by "Eric Bresie (JIRA)" <ji...@apache.org> on 2019/02/03 16:46:01 UTC
[jira] [Comment Edited] (NETBEANS-168) Background scanning process
needs a rethink
[ https://issues.apache.org/jira/browse/NETBEANS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759470#comment-16759470 ]
Eric Bresie edited comment on NETBEANS-168 at 2/3/19 4:45 PM:
--------------------------------------------------------------
Does this in any way relate to other background process/cpu issues like:
# NETBEANS-1864 Background Scanning got stuck
# NETBEANS-1939 Silent exception thrown during background scanning of projects
# NETBEANS-1629 there is a memory overflow error when background scanning is going on, mainly for large projects/projects within projects or when there are many projects open
# NETBEANS-1929 Hangs during the "Background scanning the projects" (resolved)
# NETBEANS-1142 Exception when scanning projects
# NETBEANS-1668 Netbeans Appears to Become Unresponsive
# NETBEANS-1610 Constant background CPU usage
# NETBEANS-485 OutOfMemoryError after background scanning of local Maven repository
# NETBEANS-416 Excessive CPU usage
was (Author: ebresie):
Does this in any way relate to other background process/cpu issues like:
# NETBEANS-1864 Background Scanning got stuck
# NETBEANS-1939 Silent exception thrown during background scanning of projects
# NETBEANS-1629 there is a memory overflow error when background scanning is going on, mainly for large projects/projects within projects or when there are many projects open
# NETBEANS-1929 Hangs during the "Background scanning the projects" (resolved)
# NETBEANS-1142 Exception when scanning projects
# NETBEANS-1668 Netbeans Appears to Become Unresponsive
# NETBEANS-1610 Constant background CPU usage
# NETBEANS-485 OutOfMemoryError after background scanning of local Maven repository
# NETBEANS-416 Excessive CPU usage
#
> 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, 9.0, 10.0
> Environment: NetBeans 8.2, Windows 10 x64
> Reporter: Christian Lenz
> Priority: Blocker
> Labels: ca_survey, pull-request-available
> Attachments: go-to-file.gif, messages - 10.0 vc3.log, messages 10.0 vc2.log, messages.log, puls.7z, ui.log, uigestures 10.0 vc, wp-dms.7z
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> 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-unsubscribe@netbeans.apache.org
For additional commands, e-mail: commits-help@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists