Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2039058 | 1.4.0 | Clifford Click | P1 | Closed | Fixed | beta |
Please refer to bug 4393451.
I can not reopen 4393451 because it's duplicate bug. So I filed a new one
but for the same failure.
june.zhong@eng 2000-12-04
-----------------------------------------------------------------------------
I've examined this failure and it looks to be the same failure as the
undiagnosed failures in 4390229 (core deleted before examinition was complete).
Once again in this case a scavenge was in progress. In this case the thread
being examined was thread 200. The thread was in an opto stub with state
thread_in_native. The gc was examining the oopmap for the top level frame of
this thread and found a bad oop that caused it to segv. This sounds very
suspiciously like bug 4385976. Bug 4385976 was after b09 was built. I am closing
this bug as a duplicate of that bug and since this bug had shown up in both
b08 and b09 if I'm wrong about this it will be back again in b10 and we'll
go further with it.
steve.goldman@east 2000-11-30
In build 10, there are still some intermitten failure while scavenge was
in progress.
On machine jtgb4u2d, VolanoTest has intermitten failure.
core file available at
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtgb4u2d/VolanoTest*/core.
On machine jtgb4u2c1, VolanoTest failed intermittenly.
core file available at
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtgb4u2c1/VolanoTest*/core
VolanoMark and VolanoTest failed intermittenly on jtgbp62c.
core files available at
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtgbp62c/VolanoMark*
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtgbp62c/VolanoTest*
VolanoTest failed on jtg-i111 intermittenly.
core file available at
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtg-i111/VolanoTest*/core
june.zhong@eng 2000-12-04
I can not reopen 4393451 because it's duplicate bug. So I filed a new one
but for the same failure.
june.zhong@eng 2000-12-04
-----------------------------------------------------------------------------
I've examined this failure and it looks to be the same failure as the
undiagnosed failures in 4390229 (core deleted before examinition was complete).
Once again in this case a scavenge was in progress. In this case the thread
being examined was thread 200. The thread was in an opto stub with state
thread_in_native. The gc was examining the oopmap for the top level frame of
this thread and found a bad oop that caused it to segv. This sounds very
suspiciously like bug 4385976. Bug 4385976 was after b09 was built. I am closing
this bug as a duplicate of that bug and since this bug had shown up in both
b08 and b09 if I'm wrong about this it will be back again in b10 and we'll
go further with it.
steve.goldman@east 2000-11-30
In build 10, there are still some intermitten failure while scavenge was
in progress.
On machine jtgb4u2d, VolanoTest has intermitten failure.
core file available at
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtgb4u2d/VolanoTest*/core.
On machine jtgb4u2c1, VolanoTest failed intermittenly.
core file available at
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtgb4u2c1/VolanoTest*/core
VolanoMark and VolanoTest failed intermittenly on jtgbp62c.
core files available at
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtgbp62c/VolanoMark*
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtgbp62c/VolanoTest*
VolanoTest failed on jtg-i111 intermittenly.
core file available at
/net/jtgb4u4c.eng/export/sail14/bigapps_log/solaris/ladybird_b10/jtg-i111/VolanoTest*/core
june.zhong@eng 2000-12-04
- backported by
-
JDK-2039058 VolanoTest intermitten failure during scavenge.
-
- Closed
-
- duplicates
-
JDK-4400202 RSA: JWS server hang after 21 hours 44 mins with 1.3.1beta-b12 on Solaris 2.6 (x
-
- Closed
-