I've a following up question to What is the stack size of a BackgroundWorker DoWork Thread? Is there way to change it?
Should I increase the stack size of my main program using the following post build event:
"$(DevEnvDir)..\..\VC\bin\editbin.exe" /STACK:8388608 "$(TargetPath)"
or should I capsule my recursive code block inside a new thread with a larger stack size?
Thread thread = new Thread(delegate()
{
// do work with larger stack size
}, 8192 * 1024);
thread.Start();
thread.Join();
The code which has a lot of recursion is from Intel MKLs the LAPACKE_dtrtri function which I call over DLLImport
. So I cannot change this code. I can just change the stack size to avoid a stack overflow error.
What is the draw back of assign a larger stack size to my main program?
What is the draw back of creating a new thread with a larger stack size for this calculation?
Which solution is the better one?
What would be a reasonable stack size? 8 MB, 16 MB, 32 MB or 64 MB (like MATLAB)? The program runs on computers which have at least 16 GB of RAM (up to 256 GB).
Note: for 99% of my application the default stack size of 4 MB (64-bit) would be enough but the other 1% is using external code which is heavily recursive.
The approach using
editbin
in a post-build event is failing when using strong name key to sign the assembly. After the assembly was changed usingeditbin
the verification of the signed assembly will fail.sn.exe -v assembly.exe
will returnFailed to verify assembly -- Strong name validation failed ...
See as well:
So I'm using the second approach but for the hole program and not only for the recursive code blocks:
See the comments from Hans Passant.