A co-worker had the same error the other day (In the web application though, not in AIR): Stack Overflow.
In his case it turned out to be "rampant" events. He made sure to use event.stopImmediatePropagation() when the event was no longer required to bubble and the error went away. This may not fix your problem but it is well worth doing. HTH. Steve --- In flexcoders@yahoogroups.com, "erikdebruin_nl" <erikdebruin+flexcod...@...> wrote: > > Hi, > > I've Googled me senseless, but I can't find a clue to my latest problem: > > When I run my application in the browser, all is fine. When the same app in > AIR (we've build it so the same codebase is shared between on- and offline > versions), I get an exception and the last line in the stack trace (as shown > in the Console) reads "undefined". The error dialog the player throws up > (after clicking on the "Resume (F8)" button in the debug perspective) tells > me a "stack overflow" happened. > > The "funny" thing is, when I disable the code that seems to be the cause > (taking my clues from the stack trace), the problem remains, but the stack > trace tells me another line is the problem... and so on and on. > > Google tells me that a stack overflow mostly has to do with rampant > recursion, but my app doesn't use recursion anywhere. It does however use a > lot of event chains. Do these count as "recursion"? > > What does it mean that the last line of the stack trace reads "undefined"? > > Any suggestions about further debugging my problem are very welcome! > > Thanks in advance, > > EdB >
