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: | Both actions 'Profile Class' and 'Profile Method' do not make sense | ||
---|---|---|---|
Product: | profiler | Reporter: | stwr |
Component: | Base | Assignee: | issues@profiler <issues> |
Status: | NEW --- | ||
Severity: | normal | CC: | jskrivanek |
Priority: | P3 | ||
Version: | 8.1 | ||
Hardware: | PC | ||
OS: | Windows 7 | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
stwr
2015-04-07 08:53:38 UTC
Use Case #1: 1. Open the MemoryLeakOrNot?|Example3.java 2. Select the main method in the 'Navigator' and execute the 'Profile Method' action 3. Select MemoryLeakOrNot? when asked for project to profile Result: The IDE runs the MemoryLeakOrNot? project (Example2|main) and starts profiler session for it. Should be (IMO): The IDE runs the Example3|main and starts profiler session for it. Use Case #2: 1. Open the MemoryLeakOrNot?|Example3.java 2. Select the class Example3 in the 'Navigator' and execute the 'Profile Class' action 3. Select MemoryLeakOrNot? when asked for project to profile Result: The IDE runs the MemoryLeakOrNot? project (Example2|main) and starts profiler session for it. Should be (IMO): The IDE recognizes and runs the Example3|main and starts profiler session for it. |