I add trace statements at the beginning of functions. Usually you'll see a pattern in the log.
I would also monitor memory usage. Maybe memory is being eaten while idle. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh McDonald Sent: Wednesday, December 12, 2007 3:09 PM To: [email protected] Subject: [flexcoders] Tracking down stack overflow - tips? (in a hurry unfortunately) Hi Guys, I'm getting a stack overflow somewhere in my code, and it seems that there's not one specific trigger for it as far as I can tell. It happens when I've not looked at the app for a while because I've been coding, and when I go back and click on the app it keels over and takes the browser with it (bad flash! *smack*). What are the techniques I should be using to try and track down the offending piece of code? There's nothing too funky going on in my code that I can see, no recursion or tree parsing or anything like that, so I'm sure it's just something dumb like a circular binding or similar. The problem is finding it :) Any help is definitely appreciated, as this mockup needs to go to clients Tuesday. Cheers, -Josh -- "This is crazy! Why are we talking about going to bed with Wilma Flintstone... She'll never leave Fred and we know it. " :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
