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.

Bug 95599 - Profiler IllegalStateException
Summary: Profiler IllegalStateException
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All Linux
: P4 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-14 18:53 UTC by lttldrgn
Modified: 2007-09-12 02:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
netbeans log file (40.81 KB, text/plain)
2007-02-14 19:03 UTC, lttldrgn
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lttldrgn 2007-02-14 18:53:47 UTC
Received an IllegalStateException trying to run profiler:

Steps leading to exception:
1) Select "Profile main project" from Profile menu
2) Select "Analyze Performance"
3) Select "Part of Application" and then click the Select button
4) When dialog pops up, "Add From Project"
5) When the "Select Methods" dialog comes up, click the "Select..." button

This causes the exception to be thrown.

This also happens under the "Analyze Code Fragment Performance" task.

When I received this exception I had four projects open, two java projects and
two UML projects.  I tracked this down to being related to having UML projects
open when I try to profile because after closing the UML projects I no longer
receive the exception, but upon opening one again, the exception reappears.
Comment 1 Tomas Hurka 2007-02-14 19:01:03 UTC
Please attach message.log so we can better analyze IllegalStateException.
Comment 2 lttldrgn 2007-02-14 19:03:02 UTC
Created attachment 38508 [details]
netbeans log file
Comment 3 Tomas Hurka 2007-02-15 08:54:50 UTC
Thanks.
Comment 4 Jiri Sedlacek 2007-03-23 12:44:01 UTC
This should be fixed in 6.0 - new root methods selector has been implemented. 
Could you please verify it in your environment?
Comment 5 Jiri Sedlacek 2007-07-30 14:45:38 UTC
Cannot reproduce with the new dialog, please reopen if you experience the exception again.
Comment 6 lttldrgn 2007-09-12 02:50:43 UTC
Seems to be fixed in 6.