A customer faces with critical crash(SIGSEGV) issue in Solaris box.
That occurs in 1.3.1_14 and later.
When they backed out the fix for 5053921, their crash come not to occur
even in 1.3.1_14.

=== Customers Requests ====
R1 Is there any possibility that the fix for 5053921  causes their crash ?
   (As to "their crash", please see the report attached to this CR )
   If so, please resolve and provide the fix.
R2 If it is difficult to resolve their  crash,
   please clarify whether or not 5053921 occur only in Windows box with -XX:-UseTLE (and -server ) ?
R3 If they  try to back out the src fix for 5053921,
   Could you please let us know what Sun can predict perspective of what will happen ?
   Just thought or feelings is o.k
==========================
Posted Date : 2007-07-23 05:24:44.0

N/A

The oops_do function is stopped on an oop which has the value "8",
which the JIT unfortunately generates as the address of the length
field of a NULL array object. (More recent JITs avoid doing that.)

It appears that the failure is a direct result of the fix for 5053921.
That fix causes NULL+8 style pointers to be not recognized as derived.
Instead, NULL+8 avoided during derived oop discovery, and therefore is
later perceived as a "plain" oop, eventually causing the failure
during oops_do.

This bug should not be confused with 4645614, which has the same
failure mode, but has a different cause.
Posted Date : 2007-08-18 00:27:55.0