Thomas Wolf commented on NETBEANS-4360:

No idea what steps to take.  As indicated, it just started happening in my 
project - with no changes to NB (plugins, etc.)  It could even be that it's 
been happening for quite some time but had never caused a slow-down before now.

My connectivity while WFH for the last month has been slow - I"m basically 
using my cellphone's hotspot capability to our work laptops (no broadband at 
our new house).  I get between 5-15mb/sec.  I'm just bringing this up as the 
exception is preceded by a message from the RepositoryUpdater - in case that 
refers to some NB repository, not my own git repository.

I was hoping the problem would be apparent by looking at the stack trace.  If 
not, I can ask my boss whether I can send the project src to you.  It happens 
100% of the time after the IDE starts with the project open.


> StackOverflowException in JsParser
> ----------------------------------
>                 Key: NETBEANS-4360
>                 URL: https://issues.apache.org/jira/browse/NETBEANS-4360
>             Project: NetBeans
>          Issue Type: Bug
>    Affects Versions: 12.0, 11.3
>            Reporter: Thomas Wolf
>            Priority: Critical
>         Attachments: messages.log
> Starting the day before yesterday, with no discernible change in my NB 
> version (11.3), the IDE became first slow and then unresponsive.  After 
> restart, but before it could become unresponsive, I checked the IDE log and 
> saw a StackOverflowException.
> I downloaded 12b4 and tried it - with the same results (see IDE log w. 
> exception).  I then cleared out the application support directory as well as 
> the cache and tried again.  Same result.
> Since the application has become unusable and I have deadlines, I had to 
> switch to Visual Studio Code until this is resolved.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: commits-unsubscr...@netbeans.apache.org
For additional commands, e-mail: commits-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:

Reply via email to