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 86426 - class load hook invoked at inappropriate time
Summary: class load hook invoked at inappropriate time
Status: VERIFIED WORKSFORME
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-04 04:13 UTC by jchristi
Modified: 2007-02-07 09:34 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jchristi 2006-10-04 04:13:24 UTC 
NetBeans IDE Dev (Build 200609161800)
1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b100
Windows XP version 5.1 running on x86
en_US (nb); Cp1252


C:\dil>"c:\Program Files\Java\jdk1.6.0"\bin\jhat -J-Xmx512m -J-Xms512m
-J-agentpath:"C:\Program Files\NetBeans 6.0 Dev\profiler1\lib\deployed\jdk15\wi
ndows\profilerinterface.dll=\"C:\Program Files\NetBeans 6.0
Dev\profiler1\lib\"",5140 java_pid2860.hprof
Profiler Agent: Initializing...
Profiler Agent: Options: >"C:\Program Files\NetBeans 6.0 Dev\profiler1\lib",5140<
Profiler Agent: Initialized succesfully
Profiler Agent: Waiting for connection on port 5140 (Protocol version: 2)
Profiler Agent: Established local connection with the tool
Profiler Agent: Redefining 100 classes at idx 0, out of total 408
Profiler Agent: Redefining 100 classes at idx 100, out of total 408
Profiler Agent: Redefining 100 classes at idx 200, out of total 408
Profiler Agent: Redefining 100 classes at idx 300, out of total 408
Profiler Agent: Redefining 8 classes at idx 400, out of total 408
*** Profiler engine warning: class load hook invoked at inappropriate time for
java.lang.StringCoding$StringEncoder, loader = null
*** This class will not be instrumented unless you re-run the instrumentation
command
*** Please report this problem to feedback@profiler.netbeans.org
=============================== Stack trace =====================
java.lang.Exception: Stack trace
*** Profiler engine warning: class load hook invoked at inappropriate time for
java.lang.StackTraceElement, loader = null
*** This class will not be instrumented unless you re-run the instrumentation
command
*** Please report this problem to feedback@profiler.netbeans.org
=============================== Stack trace =====================
java.lang.Exception: Stack trace
        at java.lang.Thread.dumpStack(Thread.java:1207)
        at
com.sun.tools.profiler.server.ProfilerInterface.classLoadHook(ProfilerInterface.java:738)
        at java.lang.Throwable.getStackTraceElement(Native Method)
        at java.lang.Throwable.getOurStackTrace(Throwable.java:590)
        at java.lang.Throwable.printStackTrace(Throwable.java:463)
        at java.lang.Throwable.printStackTrace(Throwable.java:452)
        at java.lang.Thread.dumpStack(Thread.java:1207)
        at
com.sun.tools.profiler.server.ProfilerInterface.classLoadHook(ProfilerInterface.java:738)
        at java.lang.StringCoding.encode(StringCoding.java:265)
        at java.lang.StringCoding.encode(StringCoding.java:288)
        at java.lang.String.getBytes(String.java:987)
        at
com.sun.tools.profiler.server.ProfilerRuntimeCPU.writeThreadCreationEvent(ProfilerRuntimeCPU.java:353)
        at
com.sun.tools.profiler.server.ProfilerRuntimeCPUFullInstr.rootMethodEntry(ProfilerRuntimeCPUFullInstr.java:63)
        at java.lang.Class.getName(Class.java:551)
        at
com.sun.tools.profiler.server.ProfilerInterface.classLoadHook(ProfilerInterface.java:724)
        at
com.sun.tools.profiler.server.ProfilerInterface.getAndInstrumentClasses(ProfilerInterface.java:514)
        at
com.sun.tools.profiler.server.ProfilerInterface.access$1000(ProfilerInterface.java:31)
        at
com.sun.tools.profiler.server.ProfilerInterface$InitiateInstThread.run(ProfilerInterface.java:268)
=============================== End stack trace =================
        at java.lang.Thread.dumpStack(Thread.java:1207)
        at
com.sun.tools.profiler.server.ProfilerInterface.classLoadHook(ProfilerInterface.java:738)
        at java.lang.StringCoding.encode(StringCoding.java:265)
        at java.lang.StringCoding.encode(StringCoding.java:288)
        at java.lang.String.getBytes(String.java:987)
        at
com.sun.tools.profiler.server.ProfilerRuntimeCPU.writeThreadCreationEvent(ProfilerRuntimeCPU.java:353)
        at
com.sun.tools.profiler.server.ProfilerRuntimeCPUFullInstr.rootMethodEntry(ProfilerRuntimeCPUFullInstr.java:63)
        at java.lang.Class.getName(Class.java:551)
        at
com.sun.tools.profiler.server.ProfilerInterface.classLoadHook(ProfilerInterface.java:724)
        at
com.sun.tools.profiler.server.ProfilerInterface.getAndInstrumentClasses(ProfilerInterface.java:514)
        at
com.sun.tools.profiler.server.ProfilerInterface.access$1000(ProfilerInterface.java:31)
        at
com.sun.tools.profiler.server.ProfilerInterface$InitiateInstThread.run(ProfilerInterface.java:268)
=============================== End stack trace =================
Comment 1 Tomas Hurka 2006-11-21 17:44:26 UTC 
Jon, are you able to reproduce it?
Comment 2 jchristi 2006-11-21 20:47:32 UTC 
I had attachments attached to this issue specifically so you could reproduce
it... I dont know where they went.

I can try to reproduce again and re-attach again.
Comment 3 Tomas Hurka 2006-11-22 10:15:43 UTC 
It looks to me like java.lang.Class.getName() was selected as (one of) root method(s). Is it possible?
Comment 4 jchristi 2007-01-08 14:48:54 UTC 
I haven't been able to reproduce this since the most recent build.

This probably should be closed, and if ever reproduced again then reopened.
Comment 5 Tomas Hurka 2007-01-08 14:56:57 UTC 
Thanks. Please reopen if you will see it again and attach message.log.
Comment 6 Alexander Kouznetsov 2007-02-07 09:34:20 UTC 
Verified