CAP partner Jeff Kardatzke reported a crash on intel with a stack overflow exception while serializing a large object. He worked around it before we could reproduce it but sent a test case which I modified to produce a crash with the exact same symptoms. Basically if you hit the yellow zone while executing native code we disable the yellow zone but don't throw an exception. The yellow zone is only reenabled when processing exceptions, so if another stack overflow occurs before the yellow zone is reenabled then we hit the red zone and die.

Here's the test case.

import java.io.*;

public class StackTest
{
  static long depth = 0;
  public static void main(String[] args) throws Exception {
    depth = Long.parseLong(args[0]);
    try { frame0(); } catch (StackOverflowError error) { System.out.println("frame0 exception"); }
  }

  public static void frame0(long repeat) throws Exception {
    System.out.println("frame0");
    recurse();
  }

  public static void recurse() throws Exception {
    try {
      java.util.Vector top = new java.util.Vector();
      java.util.Vector curr = top;
      for (long i = 0; i < depth; i++) {
        java.util.Vector x = new java.util.Vector();
        curr.addElement(x);
        curr = x;
      }
                
      ObjectOutputStream os = new ObjectOutputStream(new
        BufferedOutputStream(new FileOutputStream("vectors.ser")));
      os.writeObject(top);
      os.close();
      System.out.println("Wrote out structure");
      ObjectInputStream is = new ObjectInputStream(new
        BufferedInputStream(new FileInputStream("vectors.ser")));
      Object o = is.readObject();
      System.out.println("Read back structure.");
    } catch (StackOverflowError error) {
      recurse();
    }
  }
}


If you run it with 1000 as the argument you should get "An unrecoverable stack overflow error has occurred."
###@###.### 2001-09-12