Performance test report that the following thread is started during 1st NetBeans startup.
*** JFluid Separate Command Execution Thread
Please don't start this thread unless profiler is invoked.
More information about the test is available via the URL specified.
I'd say this is just a subset of what Issue 154324 tracks. Shouldn't be a duplicate?
I don't think so.
Can you please reconsider your decision? I remember that in one conversation this has been mentioned as easy fix.
Fixed in profiler-main
user: Tomas Hurka <firstname.lastname@example.org>
date: Wed Nov 11 11:00:05 2009 +0100
summary: bugfix #156044, JFluid Separate Command Execution Thread is now started only when necessary