gt; 4d_tech-requ...@lists.4d.com schrieb am Thu, 15 Nov 2018 12:00:01 -0800:
>> From: Chip Scheide <4d_o...@pghrepository.org>
>> To: 4D iNug Technical <4d_tech@lists.4d.com>
>> Subject: v13 - how to manage not enough stack space error
>> Message-ID: <20181115
requ...@lists.4d.com schrieb am Thu, 15 Nov 2018 12:00:01 -0800:
>From: Chip Scheide <4d_o...@pghrepository.org>
>To: 4D iNug Technical <4d_tech@lists.4d.com>
>Subject: v13 - how to manage not enough stack space error
>Message-ID: <20181115111943838786.b0800...@pghrepository.o
Chuck,
The recursion issue is a data related issue.
When the data is good, tested and running for years, there is no memory
issue, and no crashing.
It is the bad data which is causing the issue.
-- I created a relative relationship where an animal was it's own
parent... this is/was the data probl
Chip
I have some recursion stuff I do, sometimes it hit a bad data set that caused
an infinite loop. What I have done is, created a process variable that gets
incremented at the top of the recursion process and decrements at the end. I
then put a check in my code to see if I'm more than say 3
You could keep track of memory, but why not increase size of process first.
Additionally, you could get stack memory and meory data. Call it before
exit get memory stats. You housl now have a ballpark of how much emory each
call takes. You can then perhaps use a counter.
Regards
Chuck
On Thu, No
I have a recursive routine (genology)
The routine is fine and works as expected - as long as the data is
valid.
I was working in my test data, which I have apparently F*&^%ed and the
routine recurses until I get a stack error and 4D crashes (stand alone).
How can I manage this so that I can e
6 matches
Mail list logo