Licensee reported this issue using 1.4.2 b28 on Solaris 2.8/2.9 when using
hprof:heap=dump or hprof:heap=all with SwingSet2 demo.

For both of these parameters, hprof gave the following errors for all six modes
(client/server, -Xint/comp/mixed) that he tested:

HPROF ERROR: unable to resolve a method id
HPROF ERROR: got NULL trace in obj_alloc
HPROF ERROR: unable to resolve a method id
HPROF ERROR: got NULL trace in obj_alloc
HPROF ERROR: unable to resolve a method id
HPROF ERROR: got NULL trace in obj_alloc
HPROF ERROR: unable to resolve a method id
HPROF ERROR: got NULL trace in obj_alloc
HPROF ERROR: unable to resolve a method id
HPROF ERROR: got NULL trace in obj_alloc
HPROF ERROR: class ID already in use

He says these errors were not present in the 1.4.1 JVM.
I ran the same tests on my solaris machine using 1.4.2-b28 build, but could not
reproduce it. Any ideas when these errors are raised? what is causing this? Is
there anything different in his environment compared to mine? I checked in bugtraq