D
Darryn
hi,
How do i aviod the StackOverflowException? or how do i increase it's limits?
Regards
How do i aviod the StackOverflowException? or how do i increase it's limits?
Regards
B
Bruce Wood
Most stack overflows are caused by infinite recursion loops. I would
first (strongly) suspect an error somewhere in your code.
Of course, real stack overflows do happen. They can be caused by the
following things, some of which you can do nothing about, other than
increase the stack size.
1. Deep method call nesting, usually because of deep recursion, but not
always. (By deep method call nesting I mean a method that calls a
method that calls a method... repeat hundreds of times.)
2. Methods with very large amounts of local storage (very large or very
many local variables). Unless you're using structs (see below), it's
awfully difficult to get a stack overflow this way.
3. The imprudent use of structs in .NET. Since structs are copied onto
the stack, creating huge structs and then passing them on method calls,
or declaring them as local variables in recursive methods, you chew up
stack space.
I would first suspect that you have an infinite recursive loop. If not,
then I would suspect that you have a very deeply recursing call. If
not, then I would suspect that you're using structs where you shouldn't
(and I would be very surprised because at this point possible
explanations are becoming more and more unlikely).
Fortunately, it's pretty easy to tell: just look at the call stack that
is dumped out as part of the StackOverflow. It should tell you in which
method it died, which should in turn help you decide which situation
you're facing.
If you do, in the end, have to increase the stack size... well, someone
else will have to jump in on that one.
first (strongly) suspect an error somewhere in your code.
Of course, real stack overflows do happen. They can be caused by the
following things, some of which you can do nothing about, other than
increase the stack size.
1. Deep method call nesting, usually because of deep recursion, but not
always. (By deep method call nesting I mean a method that calls a
method that calls a method... repeat hundreds of times.)
2. Methods with very large amounts of local storage (very large or very
many local variables). Unless you're using structs (see below), it's
awfully difficult to get a stack overflow this way.
3. The imprudent use of structs in .NET. Since structs are copied onto
the stack, creating huge structs and then passing them on method calls,
or declaring them as local variables in recursive methods, you chew up
stack space.
I would first suspect that you have an infinite recursive loop. If not,
then I would suspect that you have a very deeply recursing call. If
not, then I would suspect that you're using structs where you shouldn't
(and I would be very surprised because at this point possible
explanations are becoming more and more unlikely).
Fortunately, it's pretty easy to tell: just look at the call stack that
is dumped out as part of the StackOverflow. It should tell you in which
method it died, which should in turn help you decide which situation
you're facing.
If you do, in the end, have to increase the stack size... well, someone
else will have to jump in on that one.
D
Darryn
I have a Deep method call... my code is fine, there is just alot of
processing going on. I will however try and reduce the number of functions
being called to see if it helps...
processing going on. I will however try and reduce the number of functions
being called to see if it helps...
B
Bruce Wood
Hey, if you have a legitimate use for more stack, allocate more stack.
I just wanted to make sure that you first knew for sure that you needed
more stack. Lots of programmers just increase the stack size without
knowing why their programs are blowing what's available.
I searched for ".NET stack overflow" on MSDN and came up with the
following tidbits:
http://support.microsoft.com/default.aspx?scid=kb;en-us;821238
http://support.microsoft.com/default.aspx?scid=kb;en-us;326611
http://msdn.microsoft.com/library/d...y/en-us/wcechp40/html/ccrefF-SetStackSize.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_.2f.F.asp
http://support.microsoft.com/default.aspx?scid=kb;en-us;828700
http://support.microsoft.com/default.aspx?scid=kb;en-us;159339
Maybe some of that material will be of help.
I just wanted to make sure that you first knew for sure that you needed
more stack. Lots of programmers just increase the stack size without
knowing why their programs are blowing what's available.
I searched for ".NET stack overflow" on MSDN and came up with the
following tidbits:
http://support.microsoft.com/default.aspx?scid=kb;en-us;821238
http://support.microsoft.com/default.aspx?scid=kb;en-us;326611
http://msdn.microsoft.com/library/d...y/en-us/wcechp40/html/ccrefF-SetStackSize.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_.2f.F.asp
http://support.microsoft.com/default.aspx?scid=kb;en-us;828700
http://support.microsoft.com/default.aspx?scid=kb;en-us;159339
Maybe some of that material will be of help.