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: | Methods table does not contain any entries | ||
|---|---|---|---|
| Product: | profiler | Reporter: | stwr |
| Component: | Base | Assignee: | issues@profiler <issues> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 8.1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: |
Copy of messages.log
Picture showing the current behavior |
||
Created attachment 153076 [details]
Picture showing the current behavior
This is expected. If you attach profiler to already running project, main method was already executed. Correct :) |
Created attachment 153075 [details] Copy of messages.log Product Version: NetBeans IDE Dev (Build 201504020001) Java: 1.8.0_31; Java HotSpot(TM) 64-Bit Server VM 25.31-b07 Runtime: Java(TM) SE Runtime Environment 1.8.0_31-b13 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb) User directory: C:\Users\cendrowiczm\AppData\Roaming\NetBeans\dev Cache directory: C:\Users\cendrowiczm\AppData\Local\NetBeans\Cache\dev Use Case: 1. Run file (e.g. MemoryLeakOrNot?|Example4|main) 2. Profile the main method by attaching the profiler to external process 3. Lookup the 'Methods' The table 'Methods' does not contain entries. It should contain at least an entry representing the main thread like it is when profiling the entire class.