I have maven projects opened in ide. With "compile on save" option, when i execute run or debug it takes about half of a
minute in order to appear the output window. And after the output window appear with "debug:" or "run:" as the only
output, it takes again another half of minute to continue.
When waiting for run or debug the ide is not freezing, it responds ok. but my procesor is in 50% load.
What can i do to enable some logging to see what is doing in that time?
tested with 6.7 rc1,
I will download 6.7 rc2 to see if it is fixed.
Created attachment 83355 [details]
ide log file
Same behavior with 6.7 rc2
Created attachment 83356 [details]
Thread dump 1
Created attachment 83357 [details]
Thread dump 2
How can i increase the log level in netbeans to see what the ide is doing when i am waiting for the run comand to start?
logging might not reveal much, better to have threaddump and/or a Alt-Shift-Y takes a profiling snapshot (also in Memory
from the threaddumps you've sent it seems the problem could be in copying of resources before the execution. There's a
bug filed against the java infrastructure that is deleting all content from the output folder, it should only delete the
*.class files. That way we loose all resources from the project and need to copy them before Run/Debug execution.
Could it be the case? do you have a vast number of resources to copy?
Thank you for your answer!
Yes, it is from the resources stuff.
What is the issue with the deleting the output folder? I want to vote for that issue.
I was not able to find the issue and by experimenting with the code I figured it already got fixed, so I've reverted the
workaround placed there before.
Integrated into 'main-golden', will be available in build *200906111401* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Milos Kleint <firstname.lastname@example.org>
Log: #166778 only copy changed resources, not everything.
Thank you guys. It is really fast now.
The 'main-golden' thing means that we will have this fix in 6.7 ?
no, but it might appear in 6.7 bugfix release though.
The fix has been ported into the release67_fixes repository.