Welcome, Guest. Please login or register.

Author Topic: Dealing with critical out of memory situations, interaction with auto stack enlargement app ?  (Read 1921 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
Hi. Most normall programs would probably display a message saying out of memory, sorry dude can't continue, but...
In what I'm trying to do I want the program to be able to have some memory reserves, wich actually is already done. However there still is is a remote possibility of an out of memory not due to a failed allocation with AllocMem/AllocVec but due to excessive recursion. Most likely, this would be an extreme and rare situation and I even have some code there to avoid it somehow (the user can define a maximum amount of recursion for some routines) this is still not perfect so I want to know:
Is it possible for my code to interact with automatic stack enlargement patches available for 3.x or the OS code itself on AOS4/MOS so that it knows when the limit is reached ? Or it's just prone to crash in that situation ?

:pint:
\\"We made Amiga, they {bleep}ed it up\\"
 

Offline JoseTopic starter

  • Hero Member
  • *****
  • Join Date: Feb 2002
  • Posts: 2871
    • Show all replies
I'll just stick with the code I have then.. It's already out of "normall" apps to have limitation on recursion I guess so it's not that bad.

How do Windows and Mac platforms handler this BTW ?
\\"We made Amiga, they {bleep}ed it up\\"