-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
netbeans 13 pollutes the log dir with hundreds of java class dump files #3728
Comments
Please show the full error lines. I saw similar problems in the NB13 development phase and could find the issue, but without the info it is unfixable. |
Well, they are generated by the JavacParser. They could help to reproduce/fix some Javac parser issues. If you are really troubled with them the following parameter can be added in the netbeans.conf:
|
Here are those full lines:
The difference here is in two parts:
and
|
@lkishalmi After an hour of usage I got 554 files in my log dir and growing. So yes it is disturbing. It's essentially three files that each are producing several hundreds of dump files. |
@lkishalmi You option helps. However, I have to correct myself. I found the same in Netbeans 12.6 and after some weeks of usage there were over 2G of dump file data. Is your PR the right way? Since there is an option to do so why not switch off this option per default? |
The option, I've posted earlier, will just limit the number of dump files to 1 per java file. It won't turn the dumpfile creation off. If I read the code well from that point it would fill the log with WARNING level messages and nobody would like that. (Probably I shall move that loglevel to FINE as well) After all it is on @jlahoda to guide us to a better solution, if he wishes. |
I think disabling the dump files is reasonable stop gap measure. The dump files may, however, be quite useful when fixing bugs in incremental reparse and other problematic cases. Seems there may be something broken around enhanced for, will try to look into that. Thanks! |
It was observed, that NetBeans can create an excessive number of source dump files in situations, where the partial reparse verifier bails out. The VanillaPartialReparser already suppresses dumping of source files in case of exceptions if assertions are not enabled. The same logic is now applied to the activation of VerifyPartialReparse. VerifyPartialReparse has no side effects and thus can be disabled if dumping should be turned off.
It was observed, that NetBeans can create an excessive number of source dump files in situations, where the partial reparse verifier bails out. The VanillaPartialReparser already suppresses dumping of source files in case of exceptions if assertions are not enabled. The same logic is now applied to the activation of VerifyPartialReparse. VerifyPartialReparse has no side effects and thus can be disabled if dumping should be turned off.
It was observed, that NetBeans can create an excessive number of source dump files in situations, where the partial reparse verifier bails out. The VanillaPartialReparser already suppresses dumping of source files in case of exceptions if assertions are not enabled. The same logic is now applied to the activation of VerifyPartialReparse. VerifyPartialReparse has no side effects and thus can be disabled if dumping should be turned off.
…tions [#3728] Only enable VerifyPartialReparse if assertions are enabled
Apache NetBeans version
Apache NetBeans 13
What happened
Within the log directory are hundreds of java source files with some tree dump information appended. This is after one day of usage.
After the actual sourcecode of compilable classes are messages like
both lines are at first sight identical.
How to reproduce
No response
Did this work correctly in an earlier version?
Apache NetBeans 12.6
Operating System
Windows 10 64bit
JDK
16
Apache NetBeans packaging
Apache NetBeans binary zip
Anything else
It's a maven project running on java 11.
Are you willing to submit a pull request?
No
Code of Conduct
Yes
The text was updated successfully, but these errors were encountered: