CTR Posted March 7, 2012 Posted March 7, 2012 (edited) The attached mission crashes the application because of an Stack Overflow. Version: BS2 v1.1.1.1 For detailed OS and System Infos take a look at the OS-Logs inside the ZIP-File. Windows also generated a 28MB '.mdmp' File which is not included, i can upload it if needed. Happy Fixing!Logs.zipNew Mission.miz Edited March 7, 2012 by CTR added the version [sigpic][/sigpic] Flanker driver since 1996 DxDiag.txt
AtaliaA1 Posted March 8, 2012 Posted March 8, 2012 Stack Overflow is a Cache error. also known as "SwapFile" your cache file ran out of space. How is your cache set? do you allow window to manage your swapfile? or have you changed the settings in an effort to get more speed by removing your swapfile because you have so much ram you believe you do not need a swapfile? If the latter is true reset your swapfile setting to windows manged. and have fun. you always need a swapfile no matter what the gamers say. limiting your PC to gaming only doesn't work because it is a windows machine. windows needs and expects to see a swapfile. when it is moved deleted or reduced windows has fits. The no swapfile ideology is based on gaming, your PC is used for more than that and it is managed by a system that requires a swapfile. This was a Boutique Builder iBuypower rig. Until I got the tinker bug again i7 920 @3.6Mhz 12Gig Corsair XMS3 ram 1600 Nvidia 760 SLi w/4Gig DDR5 Ram Intel 310 SSD HDD 160 Gb + Western Digital 4Terabyte HDD Creative SB X-Fi HD Audio Logitech X-530 5.1 Surround Speaker System Dual Acer 32"Monitors. PSU 1200 w Thermaltake Win10 64Bit.
CTR Posted March 9, 2012 Author Posted March 9, 2012 Stack Overflow is a Cache error. also known as "SwapFile" your cache file ran out of space. How is your cache set? do you allow window to manage your swapfile? or have you changed the settings in an effort to get more speed by removing your swapfile because you have so much ram you believe you do not need a swapfile? Thank you for your reply! I am running a vanilla Win7, the swapping settings are untouched. Can you reproduce the bug, i attached a miz-file? Btw. a Stack Overflow Error is not a cache or swap file realted error. This error occures when the call stack is too high and runs out of space, eg. in a infinite recursion. The call stack memory is normally not cached or even swapped, because it is not allocated on the heap-space. Caching the call stack would slow the performance down cause changes on the call stack are quite frequent. [sigpic][/sigpic] Flanker driver since 1996 DxDiag.txt
Moa Posted March 9, 2012 Posted March 9, 2012 Btw. a Stack Overflow Error is not a cache or swap file realted error. This error occures when the call stack is too high and runs out of space, eg. in a infinite recursion. This is correct. This happens when a recursive function is called (a function/method that calls itself). Each time it is called the return address and arguments get put on the stack. This is ok provided that at some point the function stops calling itself (which it will know how to do if it modifies the arguments it passes to the next instance of itself). If the self-calls never stop then the data placed on the stack grows and grows until you run out of stack. Then you get this stack overflow error. The size of the *stack* is not related to the size of your *heap* memory. The stack size is usually set at compile time (for C/C++ programs, in Java it can be resized on program startup), and is usually around 32kB - 64kB in size (yes, that is *kilobytes*), while the heap size is whatever spare memory you have left (eg 4 GB). A stack overflow is not related to how much RAM you have on your machine, what other programs are running, or how long since you re-installed DCS. It is related to a bug in the code (or game data) that causes the recursion to occur 'infinitely' (that is, until you run out of stack space and the program can no longer continue). Recursion is a nice feature. With some effort recursive solutions can often be re-cast as iterative solutions (using loops instead of self-calls). The code for interation can be less elegant but is often much safer - and it is easier to spot cases where there is no terminating condition. Frem bitter experience I personally always prefer to use loops (even ugly ones) to elegant recursion for this reason.
AtaliaA1 Posted March 12, 2012 Posted March 12, 2012 (edited) You are in a word viewing this error from your knowlege base. This is understandable as we tend to think in recursive mannerisms as humans. Debugging a Stack Overflow A stack overflow is an error that user-mode threads can encounter. There are three possible causes for this error: A thread uses the entire stack reserved for it. This is often caused by infinite recursion. A thread cannot extend the stack because the page file is maxed out, and therefore no additional pages can be committed to extend the stack. A thread cannot extend the stack because the system is within the brief period used to extend the page file. I will bow out and allow you guys to work this one out. Good Luck. I am positive you will get to the source of this issue. But before you proceed on your tech. adventure I suggest you look here first, It may save you some time. http://forums.eagle.ru/showthread.php?t=84932&highlight=Stack+Overflow Edited March 12, 2012 by AtaliaA1 This was a Boutique Builder iBuypower rig. Until I got the tinker bug again i7 920 @3.6Mhz 12Gig Corsair XMS3 ram 1600 Nvidia 760 SLi w/4Gig DDR5 Ram Intel 310 SSD HDD 160 Gb + Western Digital 4Terabyte HDD Creative SB X-Fi HD Audio Logitech X-530 5.1 Surround Speaker System Dual Acer 32"Monitors. PSU 1200 w Thermaltake Win10 64Bit.
Recommended Posts