OptimizeIt 4.2 - Problems when profiling Swing application using JDK 1.3.1_01 with classic runtime

By: Christopher Moeller

Abstract: Workaround for problems associated with the JDK 1.3.1 classic runtime

Question:

Using OptimizeIt with JDK 1.3.1_01, I am able to profile a non-gui program, but when attempting to profile an application that uses Swing classes, the following stack trace is thrown:

OptimizeIt Profiler 4.2 build 020502 Audit System.
(c) 1997-2002 Borland.
Port is 4607
OptimizeIt generic Audit System. [Classic runtime detected]
High-resolution counter available
FATAL ERROR in nati
ve method: Leaving arrays locked on native method
return
at intuitive.audit.profiler.OIContext.getContext0(Native Method)

at
intuitive.audit.profiler.OIContext.didEnterMethod(OIContext.java:35)
at java.lang.System.getProperty(System.java:553)
at sun.awt.font.NativeFontWrapper.registerFonts(Native Method)
at
sun.java2d.SunGraphicsEnvironment.registerFontFile(SunGraphicsEnvironment.java:492)

...

abnormal program termination
Press any key to continue . . .

 

Answer:

This behavior may occurr when choosing the classic runtime. It is recommended in these cases to instead choose the hotspot runtime for the JDK. To do this, place the following VM parameter into the "Extra Java Parameters" field of the "Edit settings" dialog:

-hotspot


Server Response from: ETNASC04