Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 251696 - No hits for valid profiling point when profiling the class
No hits for valid profiling point when profiling the class
Product: platform
Classification: Unclassified
Component: JDK Problems
All All
: P3 (vote)
: 8.1
Assigned To: Antonin Nebuzelsky
Depends on:
  Show dependency treegraph
Reported: 2015-04-07 10:13 UTC by stwr
Modified: 2015-04-08 07:22 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT

Picture showing the current behavior (55.57 KB, image/png)
2015-04-07 10:13 UTC, stwr

Note You need to log in before you can comment on or make changes to this bug.
Description stwr 2015-04-07 10:13:52 UTC
Created attachment 153078 [details]
Picture showing the current behavior

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. Set profiling point 'Reset Results' at MemoryLeakOrNot?|Example4:17
2. Run MemoryLeakOrNot?|Example4|main
3. Profile the MemoryLeakOrNot?|Example4 class by attaching profiler to external process
4. Examine the results for this profiling point.

The column Results displays the string 'No results available' constantly. On the other hand the line 17 is being called constantly during the entire runtime of Example4.
Comment 1 Tomas Hurka 2015-04-07 12:11:28 UTC
'Use defined Profiling Points' setting is not propagated to ProfilingSettings.
Comment 2 Tomas Hurka 2015-04-07 13:13:03 UTC
'Use defined Profiling Points' setting is correctly propagated to ProfilingSettings.

Everything works fine if Profiling Point is moved to line 16. It looks like there is a problem with conversion from line numbers to BCI.
Comment 3 Tomas Hurka 2015-04-08 06:17:37 UTC
LineNumberTable for default constructor of Example4 class is wrong. It is already reported as JDK bug #8061778.
Comment 4 Tomas Hurka 2015-04-08 07:22:25 UTC
Profiler should be no longer affected by this JDK bug.

changeset:   285749:8bf0460092e6
user:        Tomas Hurka <>
date:        Wed Apr 08 09:14:20 2015 +0200
summary:     bugfix #251696, special case added to handle situation when endLine is the last line of the same method as startLine

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo