You need to log in before you can comment on or make changes to this bug.
X.class.newInstance() type of object creation is not recorded by the profiler. Allocation via the new operator is recorded just fine. This issue becomes more relevant the bigger the application where reflection is used more often.
This issue blocks profiling of frameworks driven beans in j2ee applications e.g. JSF. They are all created by X.class.newInstance().
We need to use JVMTI to get this information.
Fixed in trunk.
*** Issue 62476 has been marked as a duplicate of this issue. ***
Failed to verify with Product Version: NetBeans IDE Dev (Build 200709271200) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 System: SunOS version 5.10 running on x86; ISO646-US; en (nb) When I perform allocation memory profiling (each 1 object allocation, no stack traces) of attached application, it creates 1000 Object instances, but profiler shows only 17.
Created an attachment (id=49733) [details] Sample Application
This it different type of bug, since objects allocation via reflection are recorded. Please file separate issue.
Filed separate issue 117264. Please provide the steps on how to verify this issue.
msandor, could you please verify this issue?
The fact that (at least) 16 instances was recorded is the proof that objects allocated via reflection are recorded. Take a look at allocation stacktraces not only for java.lang.Objct but for example java.lang.String and you will see that objects allocated via reflection are recorded.
You're right, 16 objects out of 1000 were successfully recorded. Verified according to this information. Product Version: NetBeans IDE Dev (Build 200709271200) Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 System: SunOS version 5.10 running on x86; ISO646-US; en (nb)
