Hey I read it, it didn't answer *this* question :) I know it's started when you allocated something, I just didn't know whether the actual collection would pause the vm or if it simply went and cleaned up on another thread. I know the VM's single threaded, I just figured the player would have all sort of threads for useful stuff like rendering, watching keyboard / mouse, mark-and-sweep for the GC, etc.
But it looks like I needn't be worried, which is good news to me :) Cheers, -Josh On Thu, Sep 11, 2008 at 2:30 PM, Alex Harui <[EMAIL PROTECTED]> wrote: > Dude, read my blog J > > > > There is no background/threading in the player per-se. GC is kicked off > when try to allocate memory from the player's heap and the player is trying > to avoid asking the OS for more memory. Totally synchronous, happens during > the "new", and can delay the time until the next render. > > > > *From:* [email protected] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Josh McDonald > *Sent:* Wednesday, September 10, 2008 8:24 PM > *To:* [email protected] > *Subject:* [flexcoders] Garbage Collection question > > > > Guys, just a quick question for anybody skilled up on the voodoo - I'm not > 100% sure of a way to test this yet so I thought I'd ask: I assume the > Garabage Collector is a background thread so far as mark-and-sweep etc, but > does it do actual collecting while AVM2 is processing bytecode? I'm just > worried about bugs creeping into some funky-stuff I'm doing using the > Dictionary class :) > > -Josh > > -- > "Therefore, send not to know For whom the bell tolls. It tolls for thee." > > http://flex.joshmcdonald.info/ > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." http://flex.joshmcdonald.info/ :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
