You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Chris Wareham <ch...@chriswareham.net> on 2021/08/09 11:01:34 UTC

How to diagnose lock up with 12.5 Beta 1

Hi folks,

I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
occasional lock ups. There doesn't seem to be any particular interaction
on my part that is triggering it, and the memory usage appears to be
stable with plenty of free space.

Is it possible to attach to the running process and get a stacktrace?
I'm not seeing anything log file entries that could help me understand
the problem.

My system is:

Product Version: Apache NetBeans IDE 12.5-beta1
Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)

Regards,

Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Neil C Smith <ne...@apache.org>.
On Fri, 13 Aug 2021 at 16:51, Ernie Rael <er...@raelity.com> wrote:
>
> At https://netbeans.apache.org/participate/report-issue.html there is no
> information/notes no how to set an issue priority. Is that info around
> and can it be referenced from the Reporting Issues page?

It's at https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines

It's meant to be how we triage issues during the release process.  The
extent to which that information should be user-facing is open to
question.  A simplified version might be better?

Or we remove bug priorities from users completely and figure out a
better way for developers to triage?

Certainly my experience from release managing is that the current way
of handling JIRA issues and their priorities is not fit for purpose.

> Amusingly I was going to set this issue's priority to blocker since I
> recalled that was appropriate for an identified deadlock in the before
> time, but it happened as I was getting ready to do it.

Yes, that was me on NETBEANS-5913 after confirmation from a stack
trace in a related issue.  NETBEANS-5914 should be same status?

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Ernie Rael <er...@raelity.com>.
At https://netbeans.apache.org/participate/report-issue.html there is no 
information/notes no how to set an issue priority. Is that info around 
and can it be referenced from the Reporting Issues page?

Amusingly I was going to set this issue's priority to blocker since I 
recalled that was appropriate for an identified deadlock in the before 
time, but it happened as I was getting ready to do it.

-ernie


On 8/9/2021 4:01 AM, Chris Wareham wrote:
> Hi folks,
>
> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
> occasional lock ups. There doesn't seem to be any particular interaction
> on my part that is triggering it, and the memory usage appears to be
> stable with plenty of free space.
>
> Is it possible to attach to the running process and get a stacktrace?
> I'm not seeing anything log file entries that could help me understand
> the problem.
>
> My system is:
>
> Product Version: Apache NetBeans IDE 12.5-beta1
> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
>
> Regards,
>
> Chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Can you try with a different JDK to see if that makes a difference — just
to exclude that possibility?

Gj


On Wed, 11 Aug 2021 at 12:28, Chris Wareham <ch...@chriswareham.net> wrote:

> OK, I've just had another lock up. I wasn't able to get a thread dump
> with jstack, even using the -F flag, but succeeded with VisualVM. I've
> created a Jira issue and attached both the thread dump and log file to it:
>
> https://issues.apache.org/jira/browse/NETBEANS-5913
>
> Chris
>
> On 09/08/2021 12:01, Chris Wareham wrote:
> > Hi folks,
> >
> > I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
> > occasional lock ups. There doesn't seem to be any particular interaction
> > on my part that is triggering it, and the memory usage appears to be
> > stable with plenty of free space.
> >
> > Is it possible to attach to the running process and get a stacktrace?
> > I'm not seeing anything log file entries that could help me understand
> > the problem.
> >
> > My system is:
> >
> > Product Version: Apache NetBeans IDE 12.5-beta1
> > Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> > Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> > System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
> >
> > Regards,
> >
> > Chris
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: How to diagnose lock up with 12.5 Beta 1

Posted by Chris Wareham <ch...@chriswareham.net>.
Hi all,

Another freeze, this time with the Azul JDK 11. In the trhead dump I can 
see that it again is waiting on locks in both the AWT Event Queue and 
the Editor Parsing Loop.

I've added a new thread dump and copy of the messages.log file to the 
Jira issue.

Regards,

Chris

On 11/08/2021 15:15, Neil C Smith wrote:
> On Wed, 11 Aug 2021 at 14:19, Chris Wareham <ch...@chriswareham.net> wrote:
>> On this occasion I had just selected New -> Java Class in the Projects
>> window. However, on other occasions lockups have occurred when I've just
>> hit Ctrl-S to save some changes to a file or I've just left the IDE idle
>> for a while.
> 
> Thanks.  If/when it happens again, see what you get in the thread dump
> and see if it's stuck in either of the two places mentioned in my
> previous email.  Be good to know if either (or both) are common to all
> occurrences.
> 
> Best wishes,
> 
> Neil
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
I believe uninstalling Micronaut was a workaround here.

Gj

On Sat, 21 Aug 2021 at 15:14, Eric Bresie <eb...@gmail.com> wrote:

> Just curious what kind of features are active? Is it default Java, Java
> Web and EE, Groovy?
>
> Any particular plugins active (i.e. nb-javac, Spring-Boot, etc.)?
>
> Eric Bresie
> Ebresie@gmail.com (mailto:Ebresie@gmail.com)
>
> > On August 12, 2021 at 11:21:35 AM CDT, Chris Wareham <
> chris@chriswareham.net (mailto:chris@chriswareham.net)> wrote:
> > Hi all,
> >
> > Another freeze, this time with the Azul JDK 11. In the trhead dump I can
> > see that it again is waiting on locks in both the AWT Event Queue and
> > the Editor Parsing Loop.
> >
> > I've added a new thread dump and copy of the messages.log file to the
> > Jira issue.
> >
> > Regards,
> >
> > Chris
> >
> > On 11/08/2021 15:15 (x-apple-data-detectors://4), Neil C Smith wrote:
> > > On Wed, 11 Aug 2021 at 14:19, Chris Wareham <chris@chriswareham.net
> (mailto:chris@chriswareham.net)> wrote:
> > > > On this occasion I had just selected New -> Java Class in the
> Projects
> > > > window. However, on other occasions lockups have occurred when I've
> just
> > > > hit Ctrl-S to save some changes to a file or I've just left the IDE
> idle
> > > > for a while.
> > >
> > > Thanks. If/when it happens again, see what you get in the thread dump
> > > and see if it's stuck in either of the two places mentioned in my
> > > previous email. Be good to know if either (or both) are common to all
> > > occurrences.
> > >
> > > Best wishes,
> > >
> > > Neil
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org (mailto:
> dev-unsubscribe@netbeans.apache.org)
> > > For additional commands, e-mail: dev-help@netbeans.apache.org (mailto:
> dev-help@netbeans.apache.org)
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org (mailto:
> dev-unsubscribe@netbeans.apache.org)
> > For additional commands, e-mail: dev-help@netbeans.apache.org (mailto:
> dev-help@netbeans.apache.org)
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>

Re: Re: How to diagnose lock up with 12.5 Beta 1

Posted by Eric Bresie <eb...@gmail.com>.
Just curious what kind of features are active? Is it default Java, Java Web and EE, Groovy?

Any particular plugins active (i.e. nb-javac, Spring-Boot, etc.)?

Eric Bresie
Ebresie@gmail.com (mailto:Ebresie@gmail.com)

> On August 12, 2021 at 11:21:35 AM CDT, Chris Wareham <chris@chriswareham.net (mailto:chris@chriswareham.net)> wrote:
> Hi all,
>
> Another freeze, this time with the Azul JDK 11. In the trhead dump I can
> see that it again is waiting on locks in both the AWT Event Queue and
> the Editor Parsing Loop.
>
> I've added a new thread dump and copy of the messages.log file to the
> Jira issue.
>
> Regards,
>
> Chris
>
> On 11/08/2021 15:15 (x-apple-data-detectors://4), Neil C Smith wrote:
> > On Wed, 11 Aug 2021 at 14:19, Chris Wareham <chris@chriswareham.net (mailto:chris@chriswareham.net)> wrote:
> > > On this occasion I had just selected New -> Java Class in the Projects
> > > window. However, on other occasions lockups have occurred when I've just
> > > hit Ctrl-S to save some changes to a file or I've just left the IDE idle
> > > for a while.
> >
> > Thanks. If/when it happens again, see what you get in the thread dump
> > and see if it's stuck in either of the two places mentioned in my
> > previous email. Be good to know if either (or both) are common to all
> > occurrences.
> >
> > Best wishes,
> >
> > Neil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org (mailto:dev-unsubscribe@netbeans.apache.org)
> > For additional commands, e-mail: dev-help@netbeans.apache.org (mailto:dev-help@netbeans.apache.org)
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org (mailto:dev-unsubscribe@netbeans.apache.org)
> For additional commands, e-mail: dev-help@netbeans.apache.org (mailto:dev-help@netbeans.apache.org)
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>

Re: How to diagnose lock up with 12.5 Beta 1

Posted by Neil C Smith <ne...@apache.org>.
On Wed, 11 Aug 2021 at 14:19, Chris Wareham <ch...@chriswareham.net> wrote:
> On this occasion I had just selected New -> Java Class in the Projects
> window. However, on other occasions lockups have occurred when I've just
> hit Ctrl-S to save some changes to a file or I've just left the IDE idle
> for a while.

Thanks.  If/when it happens again, see what you get in the thread dump
and see if it's stuck in either of the two places mentioned in my
previous email.  Be good to know if either (or both) are common to all
occurrences.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Chris Wareham <ch...@chriswareham.net>.
On 11/08/2021 12:07, Neil C Smith wrote:
> On Wed, 11 Aug 2021 at 11:28, Chris Wareham <ch...@chriswareham.net> wrote:
>>
>> OK, I've just had another lock up. I wasn't able to get a thread dump
>> with jstack, even using the -F flag, but succeeded with VisualVM. I've
>> created a Jira issue and attached both the thread dump and log file to it:
>>
>> https://issues.apache.org/jira/browse/NETBEANS-5913
> 
> Can you describe (here and/or in issue) roughly what you were doing at
> the moment it locked up?
> 

Hi Neil,


On this occasion I had just selected New -> Java Class in the Projects 
window. However, on other occasions lockups have occurred when I've just 
hit Ctrl-S to save some changes to a file or I've just left the IDE idle 
for a while.

Regards,

Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Neil C Smith <ne...@apache.org>.
On Wed, 11 Aug 2021 at 17:15, Eirik Bakke <eb...@ultorg.com> wrote:
> I experienced some other deadlocks in NetBeans 12.4 before, but only on startup. After examining the thread dumps I can't immediately see if they are the same bug or not (they could very well be a separate bug). In any case, I uploaded those thread dumps here:
>
> https://issues.apache.org/jira/browse/NETBEANS-5914

I may be wrong, but it looks like all yours are a deadlock at
https://github.com/apache/netbeans/blob/master/ide/projectapi/src/org/netbeans/spi/project/support/DelegatingLookupImpl.java#L168
?

At a guess the call to setLookups in the synchronized block is a
problem as that fires a bunch of notifications?

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




RE: How to diagnose lock up with 12.5 Beta 1

Posted by Eirik Bakke <eb...@ultorg.com>.
I experienced some other deadlocks in NetBeans 12.4 before, but only on startup. After examining the thread dumps I can't immediately see if they are the same bug or not (they could very well be a separate bug). In any case, I uploaded those thread dumps here:

https://issues.apache.org/jira/browse/NETBEANS-5914

-- Eirik

-----Original Message-----
From: Geertjan Wielenga <ge...@googlemail.com.INVALID> 
Sent: Wednesday, August 11, 2021 5:20 PM
To: dev <de...@netbeans.apache.org>
Subject: Re: How to diagnose lock up with 12.5 Beta 1

>
> Whenever I see an intermittent bug like this, though, my instinct is 
> to avoid changing my configuration, in case the bug stops being reproducible.
> Then I will never know what caused it, or when it will return...
>

Very interesting perspective. Never thought of it like that -- though it would help if it could be narrowed down some other way though.

Gj


On Wed, Aug 11, 2021 at 5:17 PM Eirik Bakke <eb...@ultorg.com> wrote:

> > However, I'm still of the view that trying to reproduce with a
> non-distro JDK build is useful.  I've had distro builds that behave 
> differently, crash in odd places, and even manage to run more than one 
> EDT at the same time.
>
> Ah, OK. I can see that it would be ideal to see thread dumps with the 
> crash from a "vanilla" OpenJDK or Zulu distribution.
>
> Whenever I see an intermittent bug like this, though, my instinct is 
> to avoid changing my configuration, in case the bug stops being reproducible.
> Then I will never know what caused it, or when it will return...
>
> -- Eirik
>
> -----Original Message-----
> From: Neil C Smith <ne...@apache.org>
> Sent: Wednesday, August 11, 2021 4:25 PM
> To: dev <de...@netbeans.apache.org>
> Subject: Re: How to diagnose lock up with 12.5 Beta 1
>
> On Wed, 11 Aug 2021 at 15:09, Eirik Bakke <eb...@ultorg.com> wrote:
> >
> > But if the problem goes away with a different JDK, that doesn't mean 
> > the
> bug is in the JDK--it just means the bug cannot be reproduced.
> >
> > For example, if two different NetBeans threads acquire nested locks 
> > in opposite order, that would be a deadlock bug-
>
> True, and pointed out one possible sign of that happening already.
>
> However, I'm still of the view that trying to reproduce with a 
> non-distro JDK build is useful.  I've had distro builds that behave 
> differently, crash in odd places, and even manage to run more than one EDT at the same time.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
>
> Whenever I see an intermittent bug like this, though, my instinct is to
> avoid changing my configuration, in case the bug stops being reproducible.
> Then I will never know what caused it, or when it will return...
>

Very interesting perspective. Never thought of it like that -- though it
would help if it could be narrowed down some other way though.

Gj


On Wed, Aug 11, 2021 at 5:17 PM Eirik Bakke <eb...@ultorg.com> wrote:

> > However, I'm still of the view that trying to reproduce with a
> non-distro JDK build is useful.  I've had distro builds that behave
> differently, crash in odd places, and even manage to run more than one EDT
> at the same time.
>
> Ah, OK. I can see that it would be ideal to see thread dumps with the
> crash from a "vanilla" OpenJDK or Zulu distribution.
>
> Whenever I see an intermittent bug like this, though, my instinct is to
> avoid changing my configuration, in case the bug stops being reproducible.
> Then I will never know what caused it, or when it will return...
>
> -- Eirik
>
> -----Original Message-----
> From: Neil C Smith <ne...@apache.org>
> Sent: Wednesday, August 11, 2021 4:25 PM
> To: dev <de...@netbeans.apache.org>
> Subject: Re: How to diagnose lock up with 12.5 Beta 1
>
> On Wed, 11 Aug 2021 at 15:09, Eirik Bakke <eb...@ultorg.com> wrote:
> >
> > But if the problem goes away with a different JDK, that doesn't mean the
> bug is in the JDK--it just means the bug cannot be reproduced.
> >
> > For example, if two different NetBeans threads acquire nested locks in
> > opposite order, that would be a deadlock bug-
>
> True, and pointed out one possible sign of that happening already.
>
> However, I'm still of the view that trying to reproduce with a non-distro
> JDK build is useful.  I've had distro builds that behave differently, crash
> in odd places, and even manage to run more than one EDT at the same time.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

RE: How to diagnose lock up with 12.5 Beta 1

Posted by Eirik Bakke <eb...@ultorg.com>.
> However, I'm still of the view that trying to reproduce with a non-distro JDK build is useful.  I've had distro builds that behave differently, crash in odd places, and even manage to run more than one EDT at the same time.

Ah, OK. I can see that it would be ideal to see thread dumps with the crash from a "vanilla" OpenJDK or Zulu distribution.

Whenever I see an intermittent bug like this, though, my instinct is to avoid changing my configuration, in case the bug stops being reproducible. Then I will never know what caused it, or when it will return...

-- Eirik

-----Original Message-----
From: Neil C Smith <ne...@apache.org> 
Sent: Wednesday, August 11, 2021 4:25 PM
To: dev <de...@netbeans.apache.org>
Subject: Re: How to diagnose lock up with 12.5 Beta 1

On Wed, 11 Aug 2021 at 15:09, Eirik Bakke <eb...@ultorg.com> wrote:
>
> But if the problem goes away with a different JDK, that doesn't mean the bug is in the JDK--it just means the bug cannot be reproduced.
>
> For example, if two different NetBeans threads acquire nested locks in 
> opposite order, that would be a deadlock bug-

True, and pointed out one possible sign of that happening already.

However, I'm still of the view that trying to reproduce with a non-distro JDK build is useful.  I've had distro builds that behave differently, crash in odd places, and even manage to run more than one EDT at the same time.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Neil C Smith <ne...@apache.org>.
On Wed, 11 Aug 2021 at 15:09, Eirik Bakke <eb...@ultorg.com> wrote:
>
> But if the problem goes away with a different JDK, that doesn't mean the bug is in the JDK--it just means the bug cannot be reproduced.
>
> For example, if two different NetBeans threads acquire nested locks in opposite order, that would be a deadlock bug-

True, and pointed out one possible sign of that happening already.

However, I'm still of the view that trying to reproduce with a
non-distro JDK build is useful.  I've had distro builds that behave
differently, crash in odd places, and even manage to run more than one
EDT at the same time.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Sure, true. But surely it would be relevant to know whether JDK choice
makes a difference?

Gj

On Wed, 11 Aug 2021 at 16:09, Eirik Bakke <eb...@ultorg.com> wrote:

> But if the problem goes away with a different JDK, that doesn't mean the
> bug is in the JDK--it just means the bug cannot be reproduced.
>
> For example, if two different NetBeans threads acquire nested locks in
> opposite order, that would be a deadlock bug--but the actual deadlock would
> only occur if those two critical sections happen to run at exactly the same
> time. But it would be a bug which should be fixed in NetBeans in any case.
>
> -- Eirik
>
> -----Original Message-----
> From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
> Sent: Wednesday, August 11, 2021 3:58 PM
> To: dev@netbeans.apache.org
> Subject: Re: How to diagnose lock up with 12.5 Beta 1
>
> To exclude it from the equation, especially since the problem can’t be
> localized thus far.
>
> Gj
>
> On Wed, 11 Aug 2021 at 15:56, Eirik Bakke <eb...@ultorg.com> wrote:
>
> > Why is it useful to try a different JDK here? See my earlier comment.
> >
> > -- Eirik
> >
> > -----Original Message-----
> > From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
> > Sent: Wednesday, August 11, 2021 3:29 PM
> > To: dev@netbeans.apache.org
> > Subject: Re: How to diagnose lock up with 12.5 Beta 1
> >
> > Could you, please, see if the problem continues to occur when you use
> > a few different JDKs?
> >
> > Gj
> >
> > On Wed, 11 Aug 2021 at 15:24, Chris Wareham <ch...@chriswareham.net>
> > wrote:
> >
> > > Hi Geertjan,
> > >
> > > None of my projects use Micronaut, they are all Spring Boot based.
> > > If I do a:
> > >
> > > mvn -DincludeScope=runtime dependency:tree
> > >
> > > Then no Micronaut dependencies are showing up.
> > >
> > > Regards,
> > >
> > > Chris
> > >
> > > On 11/08/2021 12:13, Geertjan Wielenga wrote:
> > > > Looks like you’re doing something with Micronaut?
> > > >
> > > > Gj
> > > >
> > > > On Wed, 11 Aug 2021 at 13:08, Neil C Smith <ne...@apache.org>
> > > wrote:
> > > >
> > > >> On Wed, 11 Aug 2021 at 11:28, Chris Wareham
> > > >> <ch...@chriswareham.net>
> > > >> wrote:
> > > >>>
> > > >>> OK, I've just had another lock up. I wasn't able to get a thread
> > > >>> dump with jstack, even using the -F flag, but succeeded with
> > > >>> VisualVM. I've created a Jira issue and attached both the thread
> > > >>> dump and log file to
> > > >> it:
> > > >>>
> > > >>> https://issues.apache.org/jira/browse/NETBEANS-5913
> > > >>
> > > >> Can you describe (here and/or in issue) roughly what you were
> > > >> doing at the moment it locked up?
> > > >>
> > > >> This seems curious ?
> > > >>
> > > >> "AWT-EventQueue-0" #21 prio=6 os_prio=0 cpu=7380.14ms
> > > >> elapsed=307.91s
> > > >> tid=0x00007f5c54163000 nid=0x22b2 waiting on condition
> > > >> [0x00007f5c60441000]
> > > >>     java.lang.Thread.State: WAITING (parking)
> > > >>          at
> > > >> jdk.internal.misc.Unsafe.park(java.base@11.0.12/Native
> > > Method)
> > > >>          - parking to wait for  <0x000000070dd6c7b0> (a
> > > >> java.util.concurrent.locks.ReentrantLock$FairSync)
> > > >>          at
> > > java.util.concurrent.locks.LockSupport.park(java.base@11.0.12
> > > >> /LockSupport.java:194)
> > > >>          at
> > > >>
> > > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckIn
> > > te
> > > rrupt(java.base@11.0.12
> > > >> /AbstractQueuedSynchronizer.java:885)
> > > >>          at
> > > >>
> > > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(
> > > ja
> > > va.base@11.0.12
> > > >> /AbstractQueuedSynchronizer.java:917)
> > > >>          at
> > > >>
> > > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.b
> > > as
> > > e@11.0.12
> > > >> /AbstractQueuedSynchronizer.java:1240)
> > > >>          at
> > > java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.12
> > > >> /ReentrantLock.java:267)
> > > >>          at
> > > >>
> > > org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProc
> > > es
> > > sor.java:170)
> > > >>          at
> > > >>
> > > org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.j
> > > av
> > > a:81)
> > > >>          at
> > > >>
> > > org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSo
> > > ur
> > > ce.java:452)
> > > >>          at
> > > >>
> > > org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource
> > > .j
> > > ava:423)
> > > >>          at
> > > >>
> > > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvi
> > > de
> > > r.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
> > > >>          at
> > > >>
> > > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvi
> > > de
> > > r.resolve(MicronautJavaHyperlinkProvider.java:122)
> > > >>          at
> > > >>
> > > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvi
> > > de
> > > r.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
> > > >>          at
> > > >>
> > > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvi
> > > de
> > > r.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
> > > >>          at
> > > >>
> > > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(Hy
> > > pe
> > > rlinkOperation.java:266)
> > > >>          at
> > > >>
> > > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlin
> > > ki
> > > ng(HyperlinkOperation.java:224)
> > > >>          at
> > > >>
> > > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.keyPressed(Hype
> > > rl
> > > inkOperation.java:382)
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Neil
> > > >>
> > > >> -----------------------------------------------------------------
> > > >> --
> > > >> -- To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > > >> For additional commands, e-mail: dev-help@netbeans.apache.org
> > > >>
> > > >> For further information about the NetBeans mailing lists, visit:
> > > >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+list
> > > >> s
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > >
> > > --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > > For additional commands, e-mail: dev-help@netbeans.apache.org
> > >
> > > For further information about the NetBeans mailing lists, visit:
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>

RE: How to diagnose lock up with 12.5 Beta 1

Posted by Eirik Bakke <eb...@ultorg.com>.
But if the problem goes away with a different JDK, that doesn't mean the bug is in the JDK--it just means the bug cannot be reproduced. 

For example, if two different NetBeans threads acquire nested locks in opposite order, that would be a deadlock bug--but the actual deadlock would only occur if those two critical sections happen to run at exactly the same time. But it would be a bug which should be fixed in NetBeans in any case.

-- Eirik

-----Original Message-----
From: Geertjan Wielenga <ge...@googlemail.com.INVALID> 
Sent: Wednesday, August 11, 2021 3:58 PM
To: dev@netbeans.apache.org
Subject: Re: How to diagnose lock up with 12.5 Beta 1

To exclude it from the equation, especially since the problem can’t be localized thus far.

Gj

On Wed, 11 Aug 2021 at 15:56, Eirik Bakke <eb...@ultorg.com> wrote:

> Why is it useful to try a different JDK here? See my earlier comment.
>
> -- Eirik
>
> -----Original Message-----
> From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
> Sent: Wednesday, August 11, 2021 3:29 PM
> To: dev@netbeans.apache.org
> Subject: Re: How to diagnose lock up with 12.5 Beta 1
>
> Could you, please, see if the problem continues to occur when you use 
> a few different JDKs?
>
> Gj
>
> On Wed, 11 Aug 2021 at 15:24, Chris Wareham <ch...@chriswareham.net>
> wrote:
>
> > Hi Geertjan,
> >
> > None of my projects use Micronaut, they are all Spring Boot based. 
> > If I do a:
> >
> > mvn -DincludeScope=runtime dependency:tree
> >
> > Then no Micronaut dependencies are showing up.
> >
> > Regards,
> >
> > Chris
> >
> > On 11/08/2021 12:13, Geertjan Wielenga wrote:
> > > Looks like you’re doing something with Micronaut?
> > >
> > > Gj
> > >
> > > On Wed, 11 Aug 2021 at 13:08, Neil C Smith <ne...@apache.org>
> > wrote:
> > >
> > >> On Wed, 11 Aug 2021 at 11:28, Chris Wareham 
> > >> <ch...@chriswareham.net>
> > >> wrote:
> > >>>
> > >>> OK, I've just had another lock up. I wasn't able to get a thread 
> > >>> dump with jstack, even using the -F flag, but succeeded with 
> > >>> VisualVM. I've created a Jira issue and attached both the thread 
> > >>> dump and log file to
> > >> it:
> > >>>
> > >>> https://issues.apache.org/jira/browse/NETBEANS-5913
> > >>
> > >> Can you describe (here and/or in issue) roughly what you were 
> > >> doing at the moment it locked up?
> > >>
> > >> This seems curious ?
> > >>
> > >> "AWT-EventQueue-0" #21 prio=6 os_prio=0 cpu=7380.14ms 
> > >> elapsed=307.91s
> > >> tid=0x00007f5c54163000 nid=0x22b2 waiting on condition 
> > >> [0x00007f5c60441000]
> > >>     java.lang.Thread.State: WAITING (parking)
> > >>          at 
> > >> jdk.internal.misc.Unsafe.park(java.base@11.0.12/Native
> > Method)
> > >>          - parking to wait for  <0x000000070dd6c7b0> (a
> > >> java.util.concurrent.locks.ReentrantLock$FairSync)
> > >>          at
> > java.util.concurrent.locks.LockSupport.park(java.base@11.0.12
> > >> /LockSupport.java:194)
> > >>          at
> > >>
> > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckIn
> > te
> > rrupt(java.base@11.0.12
> > >> /AbstractQueuedSynchronizer.java:885)
> > >>          at
> > >>
> > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(
> > ja
> > va.base@11.0.12
> > >> /AbstractQueuedSynchronizer.java:917)
> > >>          at
> > >>
> > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.b
> > as
> > e@11.0.12
> > >> /AbstractQueuedSynchronizer.java:1240)
> > >>          at
> > java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.12
> > >> /ReentrantLock.java:267)
> > >>          at
> > >>
> > org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProc
> > es
> > sor.java:170)
> > >>          at
> > >>
> > org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.j
> > av
> > a:81)
> > >>          at
> > >>
> > org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSo
> > ur
> > ce.java:452)
> > >>          at
> > >>
> > org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource
> > .j
> > ava:423)
> > >>          at
> > >>
> > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvi
> > de
> > r.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
> > >>          at
> > >>
> > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvi
> > de
> > r.resolve(MicronautJavaHyperlinkProvider.java:122)
> > >>          at
> > >>
> > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvi
> > de
> > r.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
> > >>          at
> > >>
> > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvi
> > de
> > r.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
> > >>          at
> > >>
> > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(Hy
> > pe
> > rlinkOperation.java:266)
> > >>          at
> > >>
> > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlin
> > ki
> > ng(HyperlinkOperation.java:224)
> > >>          at
> > >>
> > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.keyPressed(Hype
> > rl
> > inkOperation.java:382)
> > >>
> > >> Thanks,
> > >>
> > >> Neil
> > >>
> > >> -----------------------------------------------------------------
> > >> --
> > >> -- To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > >> For additional commands, e-mail: dev-help@netbeans.apache.org
> > >>
> > >> For further information about the NetBeans mailing lists, visit:
> > >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+list
> > >> s
> > >>
> > >>
> > >>
> > >>
> > >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
To exclude it from the equation, especially since the problem can’t be
localized thus far.

Gj

On Wed, 11 Aug 2021 at 15:56, Eirik Bakke <eb...@ultorg.com> wrote:

> Why is it useful to try a different JDK here? See my earlier comment.
>
> -- Eirik
>
> -----Original Message-----
> From: Geertjan Wielenga <ge...@googlemail.com.INVALID>
> Sent: Wednesday, August 11, 2021 3:29 PM
> To: dev@netbeans.apache.org
> Subject: Re: How to diagnose lock up with 12.5 Beta 1
>
> Could you, please, see if the problem continues to occur when you use a
> few different JDKs?
>
> Gj
>
> On Wed, 11 Aug 2021 at 15:24, Chris Wareham <ch...@chriswareham.net>
> wrote:
>
> > Hi Geertjan,
> >
> > None of my projects use Micronaut, they are all Spring Boot based. If
> > I do a:
> >
> > mvn -DincludeScope=runtime dependency:tree
> >
> > Then no Micronaut dependencies are showing up.
> >
> > Regards,
> >
> > Chris
> >
> > On 11/08/2021 12:13, Geertjan Wielenga wrote:
> > > Looks like you’re doing something with Micronaut?
> > >
> > > Gj
> > >
> > > On Wed, 11 Aug 2021 at 13:08, Neil C Smith <ne...@apache.org>
> > wrote:
> > >
> > >> On Wed, 11 Aug 2021 at 11:28, Chris Wareham
> > >> <ch...@chriswareham.net>
> > >> wrote:
> > >>>
> > >>> OK, I've just had another lock up. I wasn't able to get a thread
> > >>> dump with jstack, even using the -F flag, but succeeded with
> > >>> VisualVM. I've created a Jira issue and attached both the thread
> > >>> dump and log file to
> > >> it:
> > >>>
> > >>> https://issues.apache.org/jira/browse/NETBEANS-5913
> > >>
> > >> Can you describe (here and/or in issue) roughly what you were doing
> > >> at the moment it locked up?
> > >>
> > >> This seems curious ?
> > >>
> > >> "AWT-EventQueue-0" #21 prio=6 os_prio=0 cpu=7380.14ms
> > >> elapsed=307.91s
> > >> tid=0x00007f5c54163000 nid=0x22b2 waiting on condition
> > >> [0x00007f5c60441000]
> > >>     java.lang.Thread.State: WAITING (parking)
> > >>          at jdk.internal.misc.Unsafe.park(java.base@11.0.12/Native
> > Method)
> > >>          - parking to wait for  <0x000000070dd6c7b0> (a
> > >> java.util.concurrent.locks.ReentrantLock$FairSync)
> > >>          at
> > java.util.concurrent.locks.LockSupport.park(java.base@11.0.12
> > >> /LockSupport.java:194)
> > >>          at
> > >>
> > java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInte
> > rrupt(java.base@11.0.12
> > >> /AbstractQueuedSynchronizer.java:885)
> > >>          at
> > >>
> > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(ja
> > va.base@11.0.12
> > >> /AbstractQueuedSynchronizer.java:917)
> > >>          at
> > >>
> > java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.bas
> > e@11.0.12
> > >> /AbstractQueuedSynchronizer.java:1240)
> > >>          at
> > java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.12
> > >> /ReentrantLock.java:267)
> > >>          at
> > >>
> > org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProces
> > sor.java:170)
> > >>          at
> > >>
> > org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.jav
> > a:81)
> > >>          at
> > >>
> > org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSour
> > ce.java:452)
> > >>          at
> > >>
> > org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.j
> > ava:423)
> > >>          at
> > >>
> > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvide
> > r.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
> > >>          at
> > >>
> > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvide
> > r.resolve(MicronautJavaHyperlinkProvider.java:122)
> > >>          at
> > >>
> > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvide
> > r.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
> > >>          at
> > >>
> > org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvide
> > r.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
> > >>          at
> > >>
> > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(Hype
> > rlinkOperation.java:266)
> > >>          at
> > >>
> > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlinki
> > ng(HyperlinkOperation.java:224)
> > >>          at
> > >>
> > org.netbeans.lib.editor.hyperlink.HyperlinkOperation.keyPressed(Hyperl
> > inkOperation.java:382)
> > >>
> > >> Thanks,
> > >>
> > >> Neil
> > >>
> > >> -------------------------------------------------------------------
> > >> -- To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > >> For additional commands, e-mail: dev-help@netbeans.apache.org
> > >>
> > >> For further information about the NetBeans mailing lists, visit:
> > >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >>
> > >>
> > >>
> > >>
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

RE: How to diagnose lock up with 12.5 Beta 1

Posted by Eirik Bakke <eb...@ultorg.com>.
Why is it useful to try a different JDK here? See my earlier comment.

-- Eirik 

-----Original Message-----
From: Geertjan Wielenga <ge...@googlemail.com.INVALID> 
Sent: Wednesday, August 11, 2021 3:29 PM
To: dev@netbeans.apache.org
Subject: Re: How to diagnose lock up with 12.5 Beta 1

Could you, please, see if the problem continues to occur when you use a few different JDKs?

Gj

On Wed, 11 Aug 2021 at 15:24, Chris Wareham <ch...@chriswareham.net> wrote:

> Hi Geertjan,
>
> None of my projects use Micronaut, they are all Spring Boot based. If 
> I do a:
>
> mvn -DincludeScope=runtime dependency:tree
>
> Then no Micronaut dependencies are showing up.
>
> Regards,
>
> Chris
>
> On 11/08/2021 12:13, Geertjan Wielenga wrote:
> > Looks like you’re doing something with Micronaut?
> >
> > Gj
> >
> > On Wed, 11 Aug 2021 at 13:08, Neil C Smith <ne...@apache.org>
> wrote:
> >
> >> On Wed, 11 Aug 2021 at 11:28, Chris Wareham 
> >> <ch...@chriswareham.net>
> >> wrote:
> >>>
> >>> OK, I've just had another lock up. I wasn't able to get a thread 
> >>> dump with jstack, even using the -F flag, but succeeded with 
> >>> VisualVM. I've created a Jira issue and attached both the thread 
> >>> dump and log file to
> >> it:
> >>>
> >>> https://issues.apache.org/jira/browse/NETBEANS-5913
> >>
> >> Can you describe (here and/or in issue) roughly what you were doing 
> >> at the moment it locked up?
> >>
> >> This seems curious ?
> >>
> >> "AWT-EventQueue-0" #21 prio=6 os_prio=0 cpu=7380.14ms 
> >> elapsed=307.91s
> >> tid=0x00007f5c54163000 nid=0x22b2 waiting on condition 
> >> [0x00007f5c60441000]
> >>     java.lang.Thread.State: WAITING (parking)
> >>          at jdk.internal.misc.Unsafe.park(java.base@11.0.12/Native
> Method)
> >>          - parking to wait for  <0x000000070dd6c7b0> (a
> >> java.util.concurrent.locks.ReentrantLock$FairSync)
> >>          at
> java.util.concurrent.locks.LockSupport.park(java.base@11.0.12
> >> /LockSupport.java:194)
> >>          at
> >>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInte
> rrupt(java.base@11.0.12
> >> /AbstractQueuedSynchronizer.java:885)
> >>          at
> >>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(ja
> va.base@11.0.12
> >> /AbstractQueuedSynchronizer.java:917)
> >>          at
> >>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.bas
> e@11.0.12
> >> /AbstractQueuedSynchronizer.java:1240)
> >>          at
> java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.12
> >> /ReentrantLock.java:267)
> >>          at
> >>
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProces
> sor.java:170)
> >>          at
> >>
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.jav
> a:81)
> >>          at
> >>
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSour
> ce.java:452)
> >>          at
> >>
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.j
> ava:423)
> >>          at
> >>
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvide
> r.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
> >>          at
> >>
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvide
> r.resolve(MicronautJavaHyperlinkProvider.java:122)
> >>          at
> >>
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvide
> r.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
> >>          at
> >>
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvide
> r.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
> >>          at
> >>
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(Hype
> rlinkOperation.java:266)
> >>          at
> >>
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlinki
> ng(HyperlinkOperation.java:224)
> >>          at
> >>
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.keyPressed(Hyperl
> inkOperation.java:382)
> >>
> >> Thanks,
> >>
> >> Neil
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> >> For additional commands, e-mail: dev-help@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Could you, please, see if the problem continues to occur when you use a few
different JDKs?

Gj

On Wed, 11 Aug 2021 at 15:24, Chris Wareham <ch...@chriswareham.net> wrote:

> Hi Geertjan,
>
> None of my projects use Micronaut, they are all Spring Boot based. If I
> do a:
>
> mvn -DincludeScope=runtime dependency:tree
>
> Then no Micronaut dependencies are showing up.
>
> Regards,
>
> Chris
>
> On 11/08/2021 12:13, Geertjan Wielenga wrote:
> > Looks like you’re doing something with Micronaut?
> >
> > Gj
> >
> > On Wed, 11 Aug 2021 at 13:08, Neil C Smith <ne...@apache.org>
> wrote:
> >
> >> On Wed, 11 Aug 2021 at 11:28, Chris Wareham <ch...@chriswareham.net>
> >> wrote:
> >>>
> >>> OK, I've just had another lock up. I wasn't able to get a thread dump
> >>> with jstack, even using the -F flag, but succeeded with VisualVM. I've
> >>> created a Jira issue and attached both the thread dump and log file to
> >> it:
> >>>
> >>> https://issues.apache.org/jira/browse/NETBEANS-5913
> >>
> >> Can you describe (here and/or in issue) roughly what you were doing at
> >> the moment it locked up?
> >>
> >> This seems curious ?
> >>
> >> "AWT-EventQueue-0" #21 prio=6 os_prio=0 cpu=7380.14ms elapsed=307.91s
> >> tid=0x00007f5c54163000 nid=0x22b2 waiting on condition
> >> [0x00007f5c60441000]
> >>     java.lang.Thread.State: WAITING (parking)
> >>          at jdk.internal.misc.Unsafe.park(java.base@11.0.12/Native
> Method)
> >>          - parking to wait for  <0x000000070dd6c7b0> (a
> >> java.util.concurrent.locks.ReentrantLock$FairSync)
> >>          at
> java.util.concurrent.locks.LockSupport.park(java.base@11.0.12
> >> /LockSupport.java:194)
> >>          at
> >>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.12
> >> /AbstractQueuedSynchronizer.java:885)
> >>          at
> >>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.12
> >> /AbstractQueuedSynchronizer.java:917)
> >>          at
> >>
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.12
> >> /AbstractQueuedSynchronizer.java:1240)
> >>          at
> java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.12
> >> /ReentrantLock.java:267)
> >>          at
> >>
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:170)
> >>          at
> >>
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
> >>          at
> >>
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:452)
> >>          at
> >>
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
> >>          at
> >>
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
> >>          at
> >>
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.resolve(MicronautJavaHyperlinkProvider.java:122)
> >>          at
> >>
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
> >>          at
> >>
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
> >>          at
> >>
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(HyperlinkOperation.java:266)
> >>          at
> >>
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlinking(HyperlinkOperation.java:224)
> >>          at
> >>
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.keyPressed(HyperlinkOperation.java:382)
> >>
> >> Thanks,
> >>
> >> Neil
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> >> For additional commands, e-mail: dev-help@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: How to diagnose lock up with 12.5 Beta 1

Posted by Chris Wareham <ch...@chriswareham.net>.
Hi Geertjan,

None of my projects use Micronaut, they are all Spring Boot based. If I 
do a:

mvn -DincludeScope=runtime dependency:tree

Then no Micronaut dependencies are showing up.

Regards,

Chris

On 11/08/2021 12:13, Geertjan Wielenga wrote:
> Looks like you’re doing something with Micronaut?
> 
> Gj
> 
> On Wed, 11 Aug 2021 at 13:08, Neil C Smith <ne...@apache.org> wrote:
> 
>> On Wed, 11 Aug 2021 at 11:28, Chris Wareham <ch...@chriswareham.net>
>> wrote:
>>>
>>> OK, I've just had another lock up. I wasn't able to get a thread dump
>>> with jstack, even using the -F flag, but succeeded with VisualVM. I've
>>> created a Jira issue and attached both the thread dump and log file to
>> it:
>>>
>>> https://issues.apache.org/jira/browse/NETBEANS-5913
>>
>> Can you describe (here and/or in issue) roughly what you were doing at
>> the moment it locked up?
>>
>> This seems curious ?
>>
>> "AWT-EventQueue-0" #21 prio=6 os_prio=0 cpu=7380.14ms elapsed=307.91s
>> tid=0x00007f5c54163000 nid=0x22b2 waiting on condition
>> [0x00007f5c60441000]
>>     java.lang.Thread.State: WAITING (parking)
>>          at jdk.internal.misc.Unsafe.park(java.base@11.0.12/Native Method)
>>          - parking to wait for  <0x000000070dd6c7b0> (a
>> java.util.concurrent.locks.ReentrantLock$FairSync)
>>          at java.util.concurrent.locks.LockSupport.park(java.base@11.0.12
>> /LockSupport.java:194)
>>          at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.12
>> /AbstractQueuedSynchronizer.java:885)
>>          at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.12
>> /AbstractQueuedSynchronizer.java:917)
>>          at
>> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.12
>> /AbstractQueuedSynchronizer.java:1240)
>>          at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.12
>> /ReentrantLock.java:267)
>>          at
>> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:170)
>>          at
>> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
>>          at
>> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:452)
>>          at
>> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
>>          at
>> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
>>          at
>> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.resolve(MicronautJavaHyperlinkProvider.java:122)
>>          at
>> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
>>          at
>> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
>>          at
>> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(HyperlinkOperation.java:266)
>>          at
>> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlinking(HyperlinkOperation.java:224)
>>          at
>> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.keyPressed(HyperlinkOperation.java:382)
>>
>> Thanks,
>>
>> Neil
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Neil C Smith <ne...@apache.org>.
On Wed, 11 Aug 2021 at 12:13, Geertjan Wielenga
<ge...@googlemail.com.invalid> wrote:
> Looks like you’re doing something with Micronaut?

I think that will run whenever the module is enabled, so whenever the
enterprise cluster is active?  Looking at the dump, the EDT appears to
be waiting on the Editor Parsing Loop, and that is stuck waiting on
something in the document?  So are the EDT and parsing loop
deadlocked?  And if so, which is calling something it shouldn't?

"Editor Parsing Loop
(12.5-beta1-c0f4399cbf5c4ea5083f4b5d4dde0193065aff79)" #27 daemon
prio=1 os_prio=0 cpu=7077.14ms elapsed=306.97s tid=0x00007f5c54544800
nid=0x22b8 in Object.wait()  [0x00007f5c128d7000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(java.base@11.0.12/Native Method)
        - waiting on <no object reference available>
        at java.lang.Object.wait(java.base@11.0.12/Object.java:328)
        at javax.swing.text.AbstractDocument.writeLock(java.desktop@11.0.12/AbstractDocument.java:1355)
        - waiting to re-lock in wait() <0x0000000710388540> (a
org.netbeans.modules.editor.NbEditorDocument)
        at org.netbeans.editor.BaseDocument.extWriteLock(BaseDocument.java:1696)
        at org.netbeans.editor.BaseDocument.atomicLockImpl(BaseDocument.java:1744)
        - waiting to re-lock in wait() <0x0000000710388540> (a
org.netbeans.modules.editor.NbEditorDocument)
        - waiting to re-lock in wait() <0x0000000710388540> (a
org.netbeans.modules.editor.NbEditorDocument)
        at org.netbeans.editor.GuardedDocument.runAtomic(GuardedDocument.java:292)
        at org.openide.text.NbDocument.runAtomic(NbDocument.java:411)
        at org.netbeans.modules.gsf.testrunner.ui.api.TestMethodController.setTestMethods(TestMethodController.java:43)
....

   Locked ownable synchronizers:
        - <0x000000070dd6c7b0> (a
java.util.concurrent.locks.ReentrantLock$FairSync)

That setTestMethods method was changed in.

https://github.com/apache/netbeans/pull/2834
https://github.com/apache/netbeans/blame/master/ide/gsf.testrunner.ui/src/org/netbeans/modules/gsf/testrunner/ui/api/TestMethodController.java#L43

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Looks like you’re doing something with Micronaut?

Gj

On Wed, 11 Aug 2021 at 13:08, Neil C Smith <ne...@apache.org> wrote:

> On Wed, 11 Aug 2021 at 11:28, Chris Wareham <ch...@chriswareham.net>
> wrote:
> >
> > OK, I've just had another lock up. I wasn't able to get a thread dump
> > with jstack, even using the -F flag, but succeeded with VisualVM. I've
> > created a Jira issue and attached both the thread dump and log file to
> it:
> >
> > https://issues.apache.org/jira/browse/NETBEANS-5913
>
> Can you describe (here and/or in issue) roughly what you were doing at
> the moment it locked up?
>
> This seems curious ?
>
> "AWT-EventQueue-0" #21 prio=6 os_prio=0 cpu=7380.14ms elapsed=307.91s
> tid=0x00007f5c54163000 nid=0x22b2 waiting on condition
> [0x00007f5c60441000]
>    java.lang.Thread.State: WAITING (parking)
>         at jdk.internal.misc.Unsafe.park(java.base@11.0.12/Native Method)
>         - parking to wait for  <0x000000070dd6c7b0> (a
> java.util.concurrent.locks.ReentrantLock$FairSync)
>         at java.util.concurrent.locks.LockSupport.park(java.base@11.0.12
> /LockSupport.java:194)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.12
> /AbstractQueuedSynchronizer.java:885)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.12
> /AbstractQueuedSynchronizer.java:917)
>         at
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.12
> /AbstractQueuedSynchronizer.java:1240)
>         at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.12
> /ReentrantLock.java:267)
>         at
> org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:170)
>         at
> org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
>         at
> org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:452)
>         at
> org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
>         at
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
>         at
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.resolve(MicronautJavaHyperlinkProvider.java:122)
>         at
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
>         at
> org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
>         at
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(HyperlinkOperation.java:266)
>         at
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlinking(HyperlinkOperation.java:224)
>         at
> org.netbeans.lib.editor.hyperlink.HyperlinkOperation.keyPressed(HyperlinkOperation.java:382)
>
> Thanks,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: How to diagnose lock up with 12.5 Beta 1

Posted by Neil C Smith <ne...@apache.org>.
On Wed, 11 Aug 2021 at 11:28, Chris Wareham <ch...@chriswareham.net> wrote:
>
> OK, I've just had another lock up. I wasn't able to get a thread dump
> with jstack, even using the -F flag, but succeeded with VisualVM. I've
> created a Jira issue and attached both the thread dump and log file to it:
>
> https://issues.apache.org/jira/browse/NETBEANS-5913

Can you describe (here and/or in issue) roughly what you were doing at
the moment it locked up?

This seems curious ?

"AWT-EventQueue-0" #21 prio=6 os_prio=0 cpu=7380.14ms elapsed=307.91s
tid=0x00007f5c54163000 nid=0x22b2 waiting on condition
[0x00007f5c60441000]
   java.lang.Thread.State: WAITING (parking)
        at jdk.internal.misc.Unsafe.park(java.base@11.0.12/Native Method)
        - parking to wait for  <0x000000070dd6c7b0> (a
java.util.concurrent.locks.ReentrantLock$FairSync)
        at java.util.concurrent.locks.LockSupport.park(java.base@11.0.12/LockSupport.java:194)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.12/AbstractQueuedSynchronizer.java:885)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.12/AbstractQueuedSynchronizer.java:917)
        at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.12/AbstractQueuedSynchronizer.java:1240)
        at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.12/ReentrantLock.java:267)
        at org.netbeans.modules.parsing.impl.TaskProcessor.runUserTask(TaskProcessor.java:170)
        at org.netbeans.modules.parsing.api.ParserManager.parse(ParserManager.java:81)
        at org.netbeans.api.java.source.JavaSource.runUserActionTaskImpl(JavaSource.java:452)
        at org.netbeans.api.java.source.JavaSource.runUserActionTask(JavaSource.java:423)
        at org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getPropertyName(MicronautJavaHyperlinkProvider.java:151)
        at org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.resolve(MicronautJavaHyperlinkProvider.java:122)
        at org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.getHyperlinkSpan(MicronautJavaHyperlinkProvider.java:85)
        at org.netbeans.modules.micronaut.hyperlink.MicronautJavaHyperlinkProvider.isHyperlinkPoint(MicronautJavaHyperlinkProvider.java:79)
        at org.netbeans.lib.editor.hyperlink.HyperlinkOperation.findProvider(HyperlinkOperation.java:266)
        at org.netbeans.lib.editor.hyperlink.HyperlinkOperation.performHyperlinking(HyperlinkOperation.java:224)
        at org.netbeans.lib.editor.hyperlink.HyperlinkOperation.keyPressed(HyperlinkOperation.java:382)

Thanks,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Chris Wareham <ch...@chriswareham.net>.
OK, I've just had another lock up. I wasn't able to get a thread dump 
with jstack, even using the -F flag, but succeeded with VisualVM. I've 
created a Jira issue and attached both the thread dump and log file to it:

https://issues.apache.org/jira/browse/NETBEANS-5913

Chris

On 09/08/2021 12:01, Chris Wareham wrote:
> Hi folks,
> 
> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
> occasional lock ups. There doesn't seem to be any particular interaction
> on my part that is triggering it, and the memory usage appears to be
> stable with plenty of free space.
> 
> Is it possible to attach to the running process and get a stacktrace?
> I'm not seeing anything log file entries that could help me understand
> the problem.
> 
> My system is:
> 
> Product Version: Apache NetBeans IDE 12.5-beta1
> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
> 
> Regards,
> 
> Chris
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Neil C Smith <ne...@apache.org>.
On Mon, 9 Aug 2021 at 12:11, Chris Wareham <ch...@chriswareham.net> wrote:
> I'll install OpenJDK 17 from Debian's repositories and try that. I get a
> lock up roughly twice a day, so I'll see if a more recent JDK makes a
> difference.

As Geertjan said, not 17, but also I would try a different vendor -
eg. Azul or AdoptOpenJDK.  I've found distro packaged JDK's a little
flaky at times, at least with Ubuntu.  You don't have to install, just
unpack and point the IDE to it with the jdkhome setting.

VisualVM could be a good, easy way to diagnose what's going on.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Probably not 17, since it hasn't been released yet.

Gj

On Mon, Aug 9, 2021 at 1:11 PM Chris Wareham <ch...@chriswareham.net> wrote:

> Hi Geertjan,
>
> I'll install OpenJDK 17 from Debian's repositories and try that. I get a
> lock up roughly twice a day, so I'll see if a more recent JDK makes a
> difference.
>
> Regards,
>
> Chris
>
> On 09/08/2021 12:06, Geertjan Wielenga wrote:
> > I'd try different versions of the JDK first, to see if doing that makes a
> > difference.
> >
> > Gj
> >
> > On Mon, Aug 9, 2021 at 1:01 PM Chris Wareham <ch...@chriswareham.net>
> wrote:
> >
> >> Hi folks,
> >>
> >> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
> >> occasional lock ups. There doesn't seem to be any particular interaction
> >> on my part that is triggering it, and the memory usage appears to be
> >> stable with plenty of free space.
> >>
> >> Is it possible to attach to the running process and get a stacktrace?
> >> I'm not seeing anything log file entries that could help me understand
> >> the problem.
> >>
> >> My system is:
> >>
> >> Product Version: Apache NetBeans IDE 12.5-beta1
> >> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> >> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> >> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
> >>
> >> Regards,
> >>
> >> Chris
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> >> For additional commands, e-mail: dev-help@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: How to diagnose lock up with 12.5 Beta 1

Posted by Chris Wareham <ch...@chriswareham.net>.
Hi Geertjan,

I'll install OpenJDK 17 from Debian's repositories and try that. I get a
lock up roughly twice a day, so I'll see if a more recent JDK makes a
difference.

Regards,

Chris

On 09/08/2021 12:06, Geertjan Wielenga wrote:
> I'd try different versions of the JDK first, to see if doing that makes a
> difference.
> 
> Gj
> 
> On Mon, Aug 9, 2021 at 1:01 PM Chris Wareham <ch...@chriswareham.net> wrote:
> 
>> Hi folks,
>>
>> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
>> occasional lock ups. There doesn't seem to be any particular interaction
>> on my part that is triggering it, and the memory usage appears to be
>> stable with plenty of free space.
>>
>> Is it possible to attach to the running process and get a stacktrace?
>> I'm not seeing anything log file entries that could help me understand
>> the problem.
>>
>> My system is:
>>
>> Product Version: Apache NetBeans IDE 12.5-beta1
>> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
>> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
>> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
>>
>> Regards,
>>
>> Chris
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
I'd try different versions of the JDK first, to see if doing that makes a
difference.

Gj

On Mon, Aug 9, 2021 at 1:01 PM Chris Wareham <ch...@chriswareham.net> wrote:

> Hi folks,
>
> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
> occasional lock ups. There doesn't seem to be any particular interaction
> on my part that is triggering it, and the memory usage appears to be
> stable with plenty of free space.
>
> Is it possible to attach to the running process and get a stacktrace?
> I'm not seeing anything log file entries that could help me understand
> the problem.
>
> My system is:
>
> Product Version: Apache NetBeans IDE 12.5-beta1
> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
>
> Regards,
>
> Chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

RE: How to diagnose lock up with 12.5 Beta 1

Posted by Eirik Bakke <eb...@ultorg.com>.
> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing occasional lock ups.

Do these lockups occur only during startup (e.g. when loading projects and the like), or long after the IDE was first started?

> I've found distro packaged JDK's a little flaky at times, at least with Ubuntu.  

When a deadlock occurs, it's probably more likely to come from a bug in NetBeans rather than a bug in the JDK. If changing the JDK appears to make the bug go away, I'd suspect it's just due to race conditions being affected by random timing changes (e.g. due to different garbage collection settings). So for debugging purposes it's better to keep using the JDK that reproduced the bug.

I find the thread dump from VisualVM to be useful for debugging deadlocks.

-- Eirik

-----Original Message-----
From: Geertjan Wielenga <ge...@googlemail.com.INVALID> 
Sent: Monday, August 9, 2021 10:26 PM
To: dev@netbeans.apache.org
Subject: Re: How to diagnose lock up with 12.5 Beta 1

Also:

https://foojay.io/pedia/thread-dump/

Gj

On Mon, 9 Aug 2021 at 22:25, Ernie Rael <er...@raelity.com> wrote:

> The following post covers several ways to get a thread dump
>
>     https://www.baeldung.com/java-thread-dump
>
> -ernie
>
> On 8/9/2021 1:06 PM, Ernie Rael wrote:
> > Lock up can usually be diagnosed with a java thread dump. Create the 
> > dump (search for how to, it's based on OS), attach it to a bug 
> > report, post a message in this list that the dump is available. 
> > Sometimes multiple dumps can be useful, add them to the bug report 
> > as you get them. NetBeans log attached to the bug report can also be useful.
> >
> > -ernie
> >
> > On 8/9/2021 4:01 AM, Chris Wareham wrote:
> >> Hi folks,
> >>
> >> I've been using 12.5 Beta 1 for a couple of days, and I'm 
> >> experiencing occasional lock ups. There doesn't seem to be any 
> >> particular interaction on my part that is triggering it, and the 
> >> memory usage appears to be stable with plenty of free space.
> >>
> >> Is it possible to attach to the running process and get a stacktrace?
> >> I'm not seeing anything log file entries that could help me 
> >> understand the problem.
> >>
> >> My system is:
> >>
> >> Product Version: Apache NetBeans IDE 12.5-beta1
> >> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> >> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> >> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB 
> >> (nb)
> >>
> >> Regards,
> >>
> >> Chris
> >>
> >> -------------------------------------------------------------------
> >> -- To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> >> For additional commands, e-mail: dev-help@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >>
> >
> >
> > --------------------------------------------------------------------
> > - To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: How to diagnose lock up with 12.5 Beta 1

Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Also:

https://foojay.io/pedia/thread-dump/

Gj

On Mon, 9 Aug 2021 at 22:25, Ernie Rael <er...@raelity.com> wrote:

> The following post covers several ways to get a thread dump
>
>     https://www.baeldung.com/java-thread-dump
>
> -ernie
>
> On 8/9/2021 1:06 PM, Ernie Rael wrote:
> > Lock up can usually be diagnosed with a java thread dump. Create the
> > dump (search for how to, it's based on OS), attach it to a bug report,
> > post a message in this list that the dump is available. Sometimes
> > multiple dumps can be useful, add them to the bug report as you get
> > them. NetBeans log attached to the bug report can also be useful.
> >
> > -ernie
> >
> > On 8/9/2021 4:01 AM, Chris Wareham wrote:
> >> Hi folks,
> >>
> >> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
> >> occasional lock ups. There doesn't seem to be any particular interaction
> >> on my part that is triggering it, and the memory usage appears to be
> >> stable with plenty of free space.
> >>
> >> Is it possible to attach to the running process and get a stacktrace?
> >> I'm not seeing anything log file entries that could help me understand
> >> the problem.
> >>
> >> My system is:
> >>
> >> Product Version: Apache NetBeans IDE 12.5-beta1
> >> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> >> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> >> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
> >>
> >> Regards,
> >>
> >> Chris
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> >> For additional commands, e-mail: dev-help@netbeans.apache.org
> >>
> >> For further information about the NetBeans mailing lists, visit:
> >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>
> >>
> >>
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> > For additional commands, e-mail: dev-help@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: How to diagnose lock up with 12.5 Beta 1

Posted by Ernie Rael <er...@raelity.com>.
The following post covers several ways to get a thread dump

    https://www.baeldung.com/java-thread-dump

-ernie

On 8/9/2021 1:06 PM, Ernie Rael wrote:
> Lock up can usually be diagnosed with a java thread dump. Create the 
> dump (search for how to, it's based on OS), attach it to a bug report, 
> post a message in this list that the dump is available. Sometimes 
> multiple dumps can be useful, add them to the bug report as you get 
> them. NetBeans log attached to the bug report can also be useful.
>
> -ernie
>
> On 8/9/2021 4:01 AM, Chris Wareham wrote:
>> Hi folks,
>>
>> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
>> occasional lock ups. There doesn't seem to be any particular interaction
>> on my part that is triggering it, and the memory usage appears to be
>> stable with plenty of free space.
>>
>> Is it possible to attach to the running process and get a stacktrace?
>> I'm not seeing anything log file entries that could help me understand
>> the problem.
>>
>> My system is:
>>
>> Product Version: Apache NetBeans IDE 12.5-beta1
>> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
>> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
>> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
>>
>> Regards,
>>
>> Chris
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
>> For additional commands, e-mail: dev-help@netbeans.apache.org
>>
>> For further information about the NetBeans mailing lists, visit:
>> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: How to diagnose lock up with 12.5 Beta 1

Posted by Ernie Rael <er...@raelity.com>.
Lock up can usually be diagnosed with a java thread dump. Create the 
dump (search for how to, it's based on OS), attach it to a bug report, 
post a message in this list that the dump is available. Sometimes 
multiple dumps can be useful, add them to the bug report as you get 
them. NetBeans log attached to the bug report can also be useful.

-ernie

On 8/9/2021 4:01 AM, Chris Wareham wrote:
> Hi folks,
>
> I've been using 12.5 Beta 1 for a couple of days, and I'm experiencing
> occasional lock ups. There doesn't seem to be any particular interaction
> on my part that is triggering it, and the memory usage appears to be
> stable with plenty of free space.
>
> Is it possible to attach to the running process and get a stacktrace?
> I'm not seeing anything log file entries that could help me understand
> the problem.
>
> My system is:
>
> Product Version: Apache NetBeans IDE 12.5-beta1
> Java: 11.0.12; OpenJDK 64-Bit Server VM 11.0.12+7-post-Debian-2
> Runtime: OpenJDK Runtime Environment 11.0.12+7-post-Debian-2
> System: Linux version 5.10.0-8-amd64 running on amd64; UTF-8; en_GB (nb)
>
> Regards,
>
> Chris
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists