Question about some Sage output in the debug log

[dflachbart]

Hi,

1) I see the following lines quite frequently in the debug log :

Sat 6/10 23:54:40.037 ZRoot is aborting this draw because its unnecessary
Sat 6/10 23:54:40.410 ZRoot is aborting this draw because its unnecessary

Can anyone tell me what this means, and what could be causing it ?


2) From time to time I get the following exception in the debug log from one of my menus:

Sat 6/10 23:55:00.834 Exception in thread "AWT-EventQueue-0" java.lang.StackOverflowError
Sat 6/10 23:55:00.836 	at sage.bz.hN(Unknown Source)
Sat 6/10 23:55:00.836 	at sage.a6.fq(Unknown Source)
Sat 6/10 23:55:00.836 	at sage.a6.for(Unknown Source)
Sat 6/10 23:55:00.837 	at sage.a6.for(Unknown Source)
Sat 6/10 23:55:00.837 	at sage.a6.for(Unknown Source)
Sat 6/10 23:55:00.837 	at sage.a6.for(Unknown Source)
Sat 6/10 23:55:00.838 	at sage.a6.for(Unknown Source)
Sat 6/10 23:55:00.838 	at sage.a6.for(Unknown Source)
Sat 6/10 23:55:00.838 	at sage.a6.for(Unknown Source)
Sat 6/10 23:55:00.838 	at sage.a6.for(Unknown Source)
[... very often repeated ...]

It looks like an indefinite loop somewhere, but it doesnt happen all the time, not consistently reproducable. Any insight in what the above obfuscated methods do, or to which widget they relate to ?


Thanks,

Dirk

[GKusnick]

#1 doesn't look like an error to me, more like an optimization. The renderer has decided that some widget's appearance hasn't changed and therefore doesn't need to be redrawn. That's my guess anyway.

For #2, try turning on Studio's Trace feature. If you've got an infinite loop in your widget code (which is what it looks like), Trace should help you pin down which widgets are involved.

[dflachbart]

Originally Posted by GKusnick

#1 doesn't look like an error to me, more like an optimization. The renderer has decided that some widget's appearance hasn't changed and therefore doesn't need to be redrawn. That's my guess anyway.

Sounds logical. I am using 'RefreshArea()' commands, so this could very well be the case ...

Originally Posted by GKusnick

For #2, try turning on Studio's Trace feature. If you've got an infinite loop in your widget code (which is what it looks like), Trace should help you pin down which widgets are involved.

Thanks for the tip Greg, again I totally forgot about this feature ... I determined that when the exception happens, the tracer shows endless alternating events of two panel widgets with [Op=Event Type=Panel]. Not quite sure how to make sense of it yet ...

Dirk