http://www.mapleprimes.com/posts/43772-Stack-Limit en-us 2026 Maplesoft, A Division of Waterloo Maple Inc. Maplesoft Document System Thu, 11 Jun 2026 06:40:43 GMT Thu, 11 Jun 2026 06:40:43 GMT The latest comments added to the Post, stack limit http://www.mapleprimes.com/images/mapleprimeswhite.jpg http://www.mapleprimes.com/posts/43772-Stack-Limit http://www.mapleprimes.com/posts/43772-Stack-Limit?ref=Feed:MaplePrimes:stack limit:Comments#comment80774 I can't help you too much with the GOT problem as I am not very familar with it. It looks like you may have found a bug, rather than an acutal problem with stack limits. However, I can explain how stack limits should work. First, Windows and Unix are different. On windows the maximum stack limit is a fixed constant. This constant is the value you identified as max in your chart. We increased this constant in Maple 10, which is why the value you found is much larger than for previous versions. You can lower the stack limit in Maple. On unix, the hard stack limit is set as part of the system configuration. Many shared unix boxes will set limits to keep one user from using all the system resources. However on many desktop linux boxes these limits are not set. It appears your linux machine does not have a hard stack limit set (or it is set to "infinity"). However you may still have a soft stack limit. A soft limit still limits the amount of stack space a process can use, but it can be adjusted by the user (up to the hard limit). When you set the stacklimit in Maple you are adjusting the soft limit. On linux you can read the "ulimit" section of the bash/sh man page or the "limit" section of the tcsh/csh man page for more information on resource limits. These limits are independent of the amount of RAM on the system. They can be set to whatever you like. However if they are set too large, a poorly written or malicious program could consume all the resources of the system and effectively halt the machine. The stack limits you describe are in kibibytes so a limit of 2937000 is almost 3 Gigs of memory. As for the error messages, (1) is basically an improved version of (4). (2) and (3) are bugs. Those cases should be printing (1). One generally does not need a large stack limit. Unless you are running very recusive functions, the default limits are usually fine. Darin -- Kernel Developer Maplesoft The latest comments added to the Post, stack limit 80774 Fri, 05 Aug 2005 22:41:38 Z dohashi dohashi http://www.mapleprimes.com/posts/43772-Stack-Limit?ref=Feed:MaplePrimes:stack limit:Comments#comment86929 <p>Yes, these stacklimit figures are from personal (nonshared) linux boxes. <strong>ulimit</strong> figures for the RH7.1 box with 1GB RAM are:</p> <pre>ulimit -a core file size (blocks) 1000000 data seg size (kbytes) unlimited file size (blocks) unlimited max locked memory (kbytes) unlimited max memory size (kbytes) unlimited open files 1024 pipe size (512 bytes) 8 stack size (kbytes) 8192 cpu time (seconds) unlimited max user processes 32767 virtual memory (kbytes) unlimited </pre> <pre>ulimit -H unlimited ulimit -S unlimited </pre> <blockquote><cite> These limits are independent of the amount of RAM on the system. They can be set to whatever you like. However if they are set too large, a poorly written or malicious program could consume all the resources of the system and effectively halt the machine. The stack limits you describe are in kibibytes so a limit of 2937000 is almost 3 Gigs of memory. </cite></blockquote> <p>So, if I understand correctly there is an "afordable limit" say, determined the amount of RAM and the size of the swap partition, I guess.</p> <p>Then for 1GB RAM and 1GB swap, what maximum value for stacklimit would you suggest? It seems that default limits are not fine for GOT calculations above some size. I would set limits as high as possible if that allows the calculations to be done (within a few hours).</p> The latest comments added to the Post, stack limit 86929 Sat, 06 Aug 2005 03:46:34 Z jakubi jakubi http://www.mapleprimes.com/posts/43772-Stack-Limit?ref=Feed:MaplePrimes:stack limit:Comments#comment90121 I still suspect that the problem you are having is not a stack limit issue. Instead it looks to me that you have found a bug in Maple or GOT, which I would suggest you report to support. If it is a bug, adjusting the stack limit will not help you solve the problem. In case it is a stack limit problem, you can disable the stacklimit check by setting stacklimit=infinity. If you do this Maple will not be able to catch stacklimit problems and the kernel will simply crash when it runs out of stack space. <CITE> So, if I understand correctly there is an "afordable limit" say, determined the amount of RAM and the size of the swap partition, I guess. </CITE> It is also determined by the risk of something going wrong. On a single user machine like yours I think the risk is relatively low. I would not change the system limits. In Maple, I'd used the default unless I had some code that would not complete. The "too many levels of recursion" message is how Maple usually reports stack limit problems. The error you received is also a possibility, although that message can also mean something else went wrong. Darin -- Kernel Developer Maplesoft The latest comments added to the Post, stack limit 90121 Mon, 08 Aug 2005 17:25:03 Z dohashi dohashi http://www.mapleprimes.com/posts/43772-Stack-Limit?ref=Feed:MaplePrimes:stack limit:Comments#comment90123 I wonder whether it is possible to monitor the stack usage along a calculation. I think that it might be useful e.g. to identify code problems and to stop calculations before they reach the limit. Alejandro The latest comments added to the Post, stack limit 90123 Tue, 09 Aug 2005 04:39:06 Z jakubi jakubi http://www.mapleprimes.com/posts/43772-Stack-Limit?ref=Feed:MaplePrimes:stack limit:Comments#comment90334 i am having a similar problem with stack limits; the way i am able to see the stack size increasing is from the "Task Manager" in WinXP. look at the "PF Usage" in Performance tab. this might help. but it appears to me that somehow even inside a simple for loop some stuff is being put on a stack (even when there are no recursive calls; looks like a bug to me). the problem is worse in Maple 9 and 10; maple 8 is managing it better (will crash after some more time; but at least better than 9 and 10). The latest comments added to the Post, stack limit 90334 Fri, 23 Sep 2005 01:16:39 Z gariki gariki