This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
profiler build 070205 jdk1.6 - delete .nbprofiler and .netbeans - run IDE - start AnagramGame sample project outside ide using jdk 1.6.0 - try dynamically attach to the application, use CPU profiling all classes, entire application - got Information message that profiler will stop because calibration wasn't done - press OK button It will be nice to start calibration automatically
Automatic calibration already works for Profile Project (== direct attach). I'm not sure if it's correct to allow it also for dynamic attach - this method is used for connecting to already running applications (in production environment) - either these application need to be somehow suspended to run the calibration without additional application overhead or the calibration data would be incorrect. I think that neither of the cases is correct. A solution might be to detect which JDK is running the application and start another instance of the JDK on background just for calibration. But I'm not sure if it's possible.
It's strange but when I perform direct attach to NB (=external application) and there is no calibration data, no automatic calibration is performed.