[Glass] Error 2252 and Topaz

[Dale Henrichs via Glass]

Okay you are getting an AlmostOutOfStack in Topaz.... to get an 
AlmostOutOfStack in JADE (or any other GCI based dev environment), you 
might have to do a `Notification enableSignalling` or explicitly handle 
the AlmostOutOfStack ... otherwise GemStone just keeps running and 
instead of getting the AlmostOutOfStack you would possibly get the 2252 
error ...

Now the AlmostOutOfStack and AlmostOutOfMemory admonitions do not mean 
that there is actually a problem - it's possible that the next operation 
will avoid the out of stack or out of memory so the admonition only 
means that you are getting close , which is why they are not enabled for 
export by default.

Seaside explicitly handles the AlmostOutOfStack with error handlers: 
WAGemStoneWalkbackErrorHandler and 
WARemoteDebuggingWalkbackErrorHandler, but in your case you are getting 
the AlmostOutOfStack while handling another error, so that protection no 
longer applies ...

Dale

On 12/05/2016 11:59 AM, BrunoBB via Glass wrote:
> Dale,
>
> In the Stack report there is call to:
> renderSummaryOn:forItem:
>
> This method at some point do:
> html output: (self getMainTextForItem: aLateralItem). "HERE is/was BUG"
>
> #getMainTextForItem: instead of returning aString was returning the
> component itself (the ^ character was missing in this method).
>
> Another thing is that in Jade the loop crash and it did not render the page.
> In Topaz the loop do not crash and produce a walkback that can be viewed in
> Jade. Maybe is the interactive nature of Jade.
>
> Anyway the bug was fixed...
>
> regards
> bruno
>
>
>
> --
> View this message in context: http://forum.world.st/Error-2252-and-Topaz-tp4925684p4925821.html
> Sent from the GLASS mailing list archive at Nabble.com.
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass