Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Wolfgang Riedmann" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: errore limit execeeded Date: Wed, 22 Sep 2021 08:30:54 +0200 Lines: 56 Message-ID: References: <92a4ca6c-102e-4d23-9380-3d510861919cn@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: individual.net /TM4lrR+ZtIu0hKo8Z7DoAx6VRtMEfEX1b2U7yGiHCI/mdhqg= Cancel-Lock: sha1:AoTak5rXAwuz6Yt4RDJfOanQ1MA= User-Agent: XanaNews/1.18.1.6 Xref: csiph.com comp.lang.clipper.visual-objects:13438 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 aurora baccio wrote: > 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 --