Alex Harui wrote > "Other" includes "Other (activities such as garbage collection, event > processing, and so on)"
It's not GC (that has it's own activity which can be seen) it's the sub section activity "Runtime Overhead" Alex Harui wrote > If you have a debugger on it, I would just wait until the app is supposed > to be idle, then set a breakpoint on debugTickler in Application.as. Then > single step and it should step you into all AS that is running. I've had > that show me things that are unexpected. Now that is a great little trick I didn't know about! Done that and its then stepping into the method staticRenderHandler on mx.Core.FTETextField.as. No call stack, it doesn't do anything, nothing is in invalidFields, so it just exits. debugTickler gets called again and we go back into staticRenderHandler. Where do I go from here? Without a call stack I can't see what's initiating this call.... -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Crippling-Lag-Windows-10-IE11-FlashPlayer-IBM-ILOG-Elixir-tp14958p14988.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
