Stack A stack, in this context, is the last in, first out buffer you place data while your program runs. Last in, first out (LIFO) means that the last thing you put in is always the first thing you get back out – if you push 2 items on the stack, ‘A’ and then ‘B’, … Read more
Check for any recusive calls for methods. Mainly it is caused when there is recursive call for a method. A simple example is public static void main(String… args) { Main main = new Main(); main.testMethod(1); } public void testMethod(int i) { testMethod(i); System.out.println(i); } Here the System.out.println(i); will be repeatedly pushed to stack when the … Read more
Open the Run Configuration for your application (Run/Run Configurations…, then look for the applications entry in ‘Java application’). The arguments tab has a text box Vm arguments, enter -Xss1m (or a bigger parameter for the maximum stack size). The default value is 512 kByte (SUN JDK 1.5 – don’t know if it varies between vendors … Read more
The observed behavior is affected by the HotSpot optimizer, however it is not the only cause. When I run the following code public static void main(String[] argv) { System.out.println(System.getProperty(“java.version”)); System.out.println(countDepth()); System.out.println(countDepth()); System.out.println(countDepth()); System.out.println(countDepth()); System.out.println(countDepth()); System.out.println(countDepth()); System.out.println(countDepth()); } static int countDepth() { try { return 1+countDepth(); } catch(StackOverflowError err) { return 0; } } with JIT … Read more
No, and it never will since Guido van Rossum prefers to be able to have proper tracebacks: Tail Recursion Elimination (2009-04-22) Final Words on Tail Calls (2009-04-27) You can manually eliminate the recursion with a transformation like this: >>> def trisum(n, csum): … while True: # Change recursion to a while loop … if n … Read more
From Microsoft: Starting with the .NET Framework version 2.0, a StackOverflowException object cannot be caught by a try-catch block and the corresponding process is terminated by default. Consequently, users are advised to write their code to detect and prevent a stack overflow. For example, if your application depends on recursion, use a counter or a … Read more
Starting with 2.0 a StackOverflow Exception can only be caught in the following circumstances. The CLR is being run in a hosted environment* where the host specifically allows for StackOverflow exceptions to be handled The stackoverflow exception is thrown by user code and not due to an actual stack overflow situation (Reference) *“hosted environment” as … Read more
Hmm… it works for me and with far less than 999MB of stack: > java -Xss4m Test 0 (Windows JDK 7, build 17.0-b05 client VM, and Linux JDK 6 – same version information as you posted)
Parameters and local variables are allocated on the stack (with reference types, the object lives on the heap and a variable in the stack references that object on the heap). The stack typically lives at the upper end of your address space and as it is used up it heads towards the bottom of the … Read more