Mailing-List: contact commits-help@netbeans.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@netbeans.incubator.apache.org
Date: Wed, 26 Jul 2017 00:52:00 +0000 (UTC)
From: "Wade Chandler (JIRA)" <jira@apache.org>
To: commits@netbeans.apache.org
Message-ID: <JIRA.13090011.1501010533000.14068.1501030320099@Atlassian.JIRA>
In-Reply-To: <JIRA.13090011.1501010533000@Atlassian.JIRA>
References: <JIRA.13090011.1501010533000@Atlassian.JIRA> <JIRA.13090011.1501010533542@jira-lw-us.apache.org>
Subject: [jira] [Commented] (NETBEANS-45) Code completion is blocked for an
 extended period of time
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 26 Jul 2017 00:52:06 -0000


    [ https://issues.apache.org/jira/browse/NETBEANS-45?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D161=
01012#comment-16101012 ]=20

Wade Chandler commented on NETBEANS-45:
---------------------------------------

[~jlahoda] It happens quite often that my Mac (i7 quad core ... 8 hyper), 1=
6 GB RAM, and SSD will spin up fans like crazy (checking CPU shows NB using=
 up many cores). Too, code completion and other items are blocked in the ID=
E. Down in my status bar there will be "Checking for external changes". I d=
o switch between the CLI (using git) and the IDE a good bit. I have waited =
hours on purpose to try to see if it would free up, and it will not, so I h=
ave taken these thread dumps during those periods. Often it will say "suspe=
nded" on the external changes scanning, and there will be some other task r=
unning, but then the external changes sticks around (as long as I ever care=
 to wait). This used to happen on Linux and Windows both, but I haven't use=
d either as my laptop in a couple years.

> Code completion is blocked for an extended period of time
> ---------------------------------------------------------
>
>                 Key: NETBEANS-45
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-45
>             Project: NetBeans
>          Issue Type: Bug
>          Components: editor - Parsing & Indexing
>    Affects Versions: 9.0
>            Reporter: Attila Kelemen
>         Attachments: callstack.csv, nb-jstack-cpu-high-checking-for-exter=
nal-changes-with-gradle-and-maven-2017-04-19-10.log.tdump, nb-jstack-cpu-hi=
gh-checking-for-external-changes-with-gradle-and-maven-2017-04-19-11.log.td=
ump, nb-jstack-cpu-high-checking-for-external-changes-with-gradle-and-maven=
-2017-04-19-12.log.tdump, nb-jstack-cpu-high-checking-for-external-changes-=
with-gradle-and-maven-2017-04-19-1.log.tdump, nb-jstack-cpu-high-checking-f=
or-external-changes-with-gradle-and-maven-2017-04-19-2.log.tdump, nb-jstack=
-cpu-high-checking-for-external-changes-with-gradle-and-maven-2017-04-19-3.=
log.tdump, nb-jstack-cpu-high-checking-for-external-changes-with-gradle-and=
-maven-2017-04-19-4.log.tdump, nb-jstack-cpu-high-checking-for-external-cha=
nges-with-gradle-and-maven-2017-04-19-5.log.tdump, nb-jstack-cpu-high-check=
ing-for-external-changes-with-gradle-and-maven-2017-04-19-6.log.tdump, nb-j=
stack-cpu-high-checking-for-external-changes-with-gradle-and-maven-2017-04-=
19-7.log.tdump, nb-jstack-cpu-high-checking-for-external-changes-with-gradl=
e-and-maven-2017-04-19-8.log.tdump, nb-jstack-cpu-high-checking-for-externa=
l-changes-with-gradle-and-maven-2017-04-19-9.log.tdump, nb-jstack-cpu-high-=
checking-for-external-changes-with-gradle-and-maven-2017-05-30-10.log, nb-j=
stack-cpu-high-checking-for-external-changes-with-gradle-and-maven-2017-05-=
30-11.log, nb-jstack-cpu-high-checking-for-external-changes-with-gradle-and=
-maven-2017-05-30-12.log, nb-jstack-cpu-high-checking-for-external-changes-=
with-gradle-and-maven-2017-05-30-1.log, nb-jstack-cpu-high-checking-for-ext=
ernal-changes-with-gradle-and-maven-2017-05-30-2.log, nb-jstack-cpu-high-ch=
ecking-for-external-changes-with-gradle-and-maven-2017-05-30-3.log, nb-jsta=
ck-cpu-high-checking-for-external-changes-with-gradle-and-maven-2017-05-30-=
4.log, nb-jstack-cpu-high-checking-for-external-changes-with-gradle-and-mav=
en-2017-05-30-5.log, nb-jstack-cpu-high-checking-for-external-changes-with-=
gradle-and-maven-2017-05-30-6.log, nb-jstack-cpu-high-checking-for-external=
-changes-with-gradle-and-maven-2017-05-30-7.log, nb-jstack-cpu-high-checkin=
g-for-external-changes-with-gradle-and-maven-2017-05-30-8.log, nb-jstack-cp=
u-high-checking-for-external-changes-with-gradle-and-maven-2017-05-30-9.log=
, nb-jstack-cpu-high-opening-gradle-and-maven-projects-2017-01-18-10.log.td=
ump, nb-jstack-cpu-high-opening-gradle-and-maven-projects-2017-01-18-11.log=
.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projects-2017-01-18-12.=
log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projects-2017-01-18-=
1.log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projects-2017-01-1=
8-2.log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projects-2017-01=
-18-3.log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projects-2017-=
01-18-4.log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projects-201=
7-01-18-5.log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projects-2=
017-01-18-6.log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projects=
-2017-01-18-7.log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-projec=
ts-2017-01-18-8.log.tdump, nb-jstack-cpu-high-opening-gradle-and-maven-proj=
ects-2017-01-18-9.log.tdump
>
>
> Often times when editting a single file, code completion blocks for an ex=
tensive amount of time which makes code completion practically unusable. Lo=
oking at the threads of the IDE, code completion and parsing seems to be bl=
ocked by the attached thread (holding a lock).
> Note that I do not do anything but edit a single file and this happens fr=
equently during editting even though there are no external changes.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)