errore limit execeeded

[aurora baccio]

Good evening to all
what does this error mean that appears during the execution of the application ?
limit exceeded
kid stack size limit exceeded
PatientWithoutRecipeMask:Choice_Ok line 35
this is line 35
FabCenterWindow(oChoice)
where oChoice is the reference Mask to recall.
This error does not appear in VOERROR. log and finally I was able to reconstruct it, but it appears in other parts of the application.
as always thanks to all.
Aurora Baccio

[Franz Rachbauer]

Maybe this helps:
https://groups.google.com/g/comp.lang.clipper.visual-objects/c/EXM73l7bhyg
Regards

[aurora baccio]

Sorry, but l don't know what to do.
Can you give me an example ?

Foto del profilo di Geoff Schaller
Geoff Schaller
24 feb 2010, 11:09:06
a
Dick,
Its simple enough. Your application is in a loop. Often this is an error
loop (where an error condition causes a consequential error condition
and so round you go) or a focus change event that goes on creating more
focus change events.

Basically you run out of axits.

You need to be throwing a calling stack on entry to where-ever this is
happening.
tkanks
Aurora Baccio

[Jamal]

This means you are calling the same method or function recursively
(calling itself) which will cause the kid stack limit to be exceeded.
Check your code.

Jamal

[Wolfgang Riedmann]

Buon giorno Aurora,

"kid stack limit exceeded" means that you have created to many objects.

Many objects are registered with the RegisterKid() function to be
retained even after a garbage collection (please see the RegisterKid()
help for a better explanation of this).

And, like any other list, also the list of registered kids has a limit,
and you are exceeding that.

And, as Jamal wrote, normally (at least in my applications) this is
occurring only when I have an endless loop (a function or method
calling itself).
Before this error is showing up, you should see that your application
becomes slow and is taking up an entire processore core ressources
(depending on your PC, the task manager should show a 20% or 25% or
even 50% CPU allocation of your application).

In my code, this is occurring when I have code like this:

method xxx() class Pippo

....
self:xxx()
....

return nil

To be honest, I have that 2 to 3 times a month, mostly when I split up
classes, and forget to change the self:xxx() to a super:xxx().

Another possibility is that you are reacting on an event, and your code
triggers that event again.

Wolfgang

--