Stack overflow is a situation when the stack is full and any item that is pushed onto it will not be incorporated and will cause stack overflow to occur. This is NOT about the website StackOverflow.com.
0
votes
1answer
208 views
What happens when both heap and stack are full?
Suppose I am using a very heavy applications(or you can say that it is a very bad code which keeps on allocating memory on heap and won't free it and also uses recursion) Now after some point of time ...
7
votes
4answers
672 views
When there's no TCO, when to worry about blowing the stack?
Every single time there's a discussion about a new programming language targetting the JVM, there are inevitably people saying things like:
"The JVM doesn't support tail-call optimization, so I ...
22
votes
2answers
2k views
Is it *ever* okay to catch StackOverflowError in Java?
I used to think that it's not, but yesterday I had to do it. It's an application that uses Akka (an actor system implementation for the JVM) to process asynchronous jobs. One of the actors performs ...
2
votes
6answers
3k views
Heap overflow vs stack overflow
So as a general rule to avoid a stack overflow, big objects should be allocated to the heap (correct me if I am wrong). But, since the heap and the stack expand towards each other, wouldn't this cause ...
15
votes
3answers
2k views
How many are too many nested function calls?
Quoted from MSDN about StackOverflowException:
The exception that is thrown when the execution stack overflows because it contains too many nested method calls.
Too many is pretty vague here. ...
19
votes
1answer
965 views
How often is seq used in Haskell production code?
I have some experience writing small tools in Haskell and I find it very intuitive to use, especially for writing filters (using interact) that process their standard input and pipe it to standard ...
