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.
|Summary:||Profile information is not full after Reset for Global Attach|
|Product:||profiler||Reporter:||Alexander Kouznetsov <mrkam>|
|Component:||Base||Assignee:||Petr Cyhelsky <cyhelsky>|
|Issue Type:||ENHANCEMENT||Exception Reporter:|
Snapshot when Anagram Project selected
Snapshot when Global Attach selected
Description Alexander Kouznetsov 2007-02-26 14:22:08 UTC
Profiler 070226 NetBeans IDE Dev (Build 200702251900) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251 Steps to reproduce: - Build Anagram Game project - Use Direct Attach with "Global Project" option to Profile it. Select Analyze Performance (Entire Application, Profile All Classes). - Open Live Results - Play with application - See what com.toy.* methods are shown - Reset collected data - Play with application - RESULT: There are no com.toy.* methods in Live Results. Try to repeat these steps performing Direct Attach with Anagram Game Project selected. In this case all com.toy.* methods will be shown in Live Results.
Comment 1 Alexander Kouznetsov 2007-02-26 14:23:15 UTC
Created attachment 38908 [details] Snapshot when Anagram Project selected
Comment 2 Alexander Kouznetsov 2007-02-26 14:23:59 UTC
Created attachment 38909 [details] Snapshot when Global Attach selected
Comment 3 J Bachorik 2007-03-19 10:10:37 UTC
Comment 4 J Bachorik 2007-03-23 13:07:55 UTC
not for m8
Comment 5 Tomas Hurka 2007-03-23 17:16:44 UTC
This is currently as designed. With Profile Project, Entire Application root methods are computed from the sources and every method in project is root method. However no such information is available with global attach so for global attach Runable.run() and first class with void main(String) are root methods. For AnagramGame no root method is invoked after your 'Reset Results'.
Comment 6 J Bachorik 2007-03-26 09:23:25 UTC
according to the previous comment closing this issue as invalid
Comment 7 Alexander Kouznetsov 2007-03-26 13:07:33 UTC
I believe this design is not transparent enough to user due to the following reasons: - Reset Results is assumed to be the way user could reset all counters of profiling. There are another ways to re-start profiling: to use Modify with the same parameters, or detach and attach profiler again. This seems to be a usability issue. - There is no clear information what side effects selection of different projects could cause (due to computation of root methods, etc.). This could cause user to fail to get relevant measurement data. This is a usability issue as well. Feel free to change this to ENHANCEMENT if all of this is as designed.
Comment 8 J Bachorik 2007-03-26 13:29:18 UTC
changing to enhancement - the application works as designed; however it can be further improved
Comment 9 Mikhail Kondratyev 2007-08-31 15:03:03 UTC
Just tried profiling the JAlbum application and could see this bug after resetting results. I was 200% sure this is a bug until Alexander has pointed me to this issue. My opinion as a user is that this behavior is a bug. I vote for fixing this as soon as possible or at least implement issue 95808 to avoid confusion
Comment 10 Tomas Hurka 2009-04-08 12:54:45 UTC
Milestone cleanup: future->next
Comment 11 J Bachorik 2012-08-01 08:33:58 UTC