JDK-4812196 : infinite recursion in AsyncGetCallTrace() with the server JVM
  • Type: Bug
  • Component: vm-legacy
  • Sub-Component: jvmpi
  • Affected Version: 1.4.2
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: sparc
  • Submitted: 2003-02-03
  • Updated: 2003-07-18
  • Resolved: 2003-06-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
1.4.2_02 02Fixed
When used with 'collect' on a fairly big MT application (NetBeans), the JVM may
crash in AsyncGetCallTrace(). All symptoms suggest that the stack overflowed.

% collect -j on java -server <app>

See Comments for a pstack generated stack trace.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.4.2_02 tiger FIXED IN: 1.4.2_02 tiger INTEGRATED IN: 1.4.2_02 tiger tiger-b08

EVALUATION Deferring to tiger. ###@###.### 2003-04-17 I fixed one infinite recursion in stack walking in the Mantis-Update batch of bug fixes. I found the thread stuck in the for-loop that walks the sender chain in forte_is_walkable_frame(). The for-loop tried walking the stack and found a self-referential frame so we just kept walking the same set of frames over and over. I have not been able to reproduce the original failure mode. Marty has agreed that we can consider this bug fixed.