Request to fix editor frozen issue to improve the performance of〈Go to Declaration〉feature

[rfrkk]

Apache NetBeans version

Apache NetBeans 13

What happened

Hi

I work as a web developer using html.css.javascript and php. I would like you to request to fix this issue to improve the performance of netbeans13.

When i use〈Go to Declaration〉feature that Netbenas13 is often frozen and editor is incapable of operation, the performance of netbeans 13 is much lower than that of netbeans 12.6.

Netbeans13 and 12.6 all i use default settings, and no installed any extra plugins, these are the videos I made:

1. netbeans13 frozen: (https://user-images.githubusercontent.com/137764/161173612-29881d36-369b-43fe-9412-7be27b64d404.mp4)
2. netbeans12.6 no frozen: (https://user-images.githubusercontent.com/137764/161171064-f133e2df-5834-4ad3-8511-7f362724acfa.mp4)

Tks.

How to reproduce

step1. Use ctrl+mouse click to go Category_model declaration.

step2. It will change to Category_model

step3. After Category_model opening , go back FendController from there immediately. Then using ctrl+mouse click to go Controller declaration, but editor is often frozen and incapable of operation until 10s later.

Did this work correctly in an earlier version?

Apache NetBeans 12.6

Operating System

windows10

JDK

java 8

Apache NetBeans packaging

Apache NetBeans binary zip

Anything else

No response

Are you willing to submit a pull request?

No

Code of Conduct

Yes

[junichi11]

@rfrkk Could you provide an example code to reproduce it?

[rfrkk]

This is an example :
https://github.com/oceanfish567/oceanfish0416/tree/master

[junichi11]

@rfrkk
Umm, I can't reproduce it in my PC (although it's Ubuntu).
Please try deleting your cache directory.

[rfrkk]

@junichi11
I delete netbeans 13 cache (C:\Users\XXXX\AppData\Local\NetBeans\Cache\13), and also delete netbeans 12.6.
But the problem still exists, neabenas forzen that cpu just usage 20%.

I just use the old version 12.6, that's ok.
tks.

[Chris2011]

I see you still using JDK 8. Is it possible for you that you can try out JDK 11 or maybe 17? I have Win 10, NB 13 and JDK 14. Didn't test your project with my WordPress project, I also can't reproduce it. Please test it with a newer JDK and let us know whether it sill exists or not :)

[rfrkk]

@Chris2011
Thank you for your assistance.
First, I re-downloaded nb13 (Binaries: netbeans-13-bin.zip (SHA-512, PGP ASC).

Second, I removed all nb cache and java sdk 8.

Third, I installed java jdk 17 and started nb13, but the test result still freezes in "Go to Declaration".

Finally, I started nb12.6, and the test results all worked smoothly. I guess it may be that the specifications of my laptop are old computers in 2015, or the architecture of nb13 is very different from nb12.6, which is the result? :)

[czukowski]

I also noticed a considerable slowdown since NB13, but I tried it with a large project (close to 40k classes). NB12.6 handled it a little better, but still quite slowly. "Go to Declaration" is generally not usable in this situation, it works sometimes, but more often it takes a lot of time to respond (sometimes freezing the UI) or shows 'Cannot refactor' message box right away. Upgrading JDK (currently OpenJDK 18 on Win10) didn't seem to make any difference 😥

[mko-callpage]

I agree, NetBeans is very slow at this and similar tasks, like autocomplete for classes (probably same reason, takes too long to resolve it).

If your project contains symlinks that could cause loops make sure to add them to ignored paths in your project config. Otherwise a temporary solution would be to increase your cache size (it makes the IDE usable, but still slow): https://stackoverflow.com/questions/28811246/netbeans-background-scanning-projects-takes-too-long/31869064#31869064

I think there are 2 problems here:

1. Big projects don't fit in cache
2. The code responsible for resolving classes is slow and needs refactoring