That's helpful, thanks (The same goes for Alex's response). I'm currently dealing with a series of intermittent .ocx errors that seem to be memory related, but never output any useful debugging information. I'm trying various memory management strategies, and though they keep popping up they're at least not as frequent anymore.
If anyone else has run into them and found ways of debugging/resolving them, I'd be very grateful for your insight. Michael Krotscheck Senior Developer RESOURCE INTERACTIVE <http://www.resource.com/> www.resource.com <http://www.resource.com> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ________________________________________________________________________ ____ This email and any of its attachments may contain Resource Interactive proprietary information, which is privileged, confidential and may be subject to copyright or other intellectual property rights belonging to Resource Interactive. This email is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this email, you are hereby notified that any dissemination, distribution, copying or action taken in relation to the contents of and attachments to this email is strictly prohibited and may be unlawful. If you have received this email in error, please notify the sender immediately and permanently delete the original and any copy of this email and any printout. ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Josh VanderBerg Sent: Saturday, November 17, 2007 7:33 PM To: [email protected] Subject: [flexcoders] Re: Garbage Collection question I've read that the GC runs only on allocation. Can't seem to find the original article I read on this, but this livedoc reference appears to agree: http://livedocs.adobe.com/labs/flex3/html/help.html?content=profiler_6.h tml <http://livedocs.adobe.com/labs/flex3/html/help.html?content=profiler_6. html> __ Josh Vanderberg vanderblog.typepad.com - Flex blog and open source flex components --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Mike Krotscheck" <[EMAIL PROTECTED]> wrote: > > I've been digging into memory management techniques recently, and have a > question regarding the timing of the two methods. The articles on > Adobe.com suggest that both methods (Ref Count and Mark & Sweep) run at > some arbitrary point in the future defined by current memory usage. I > found a discussion about the Virtual Machine though that indicated > garbage collection happens on a 30ms interval. > > > > These two suggest that the two methods run on different intervals, and > given that Mark and Sweep is more processor intensive I assume that it > is the one whose timing is triggered by memory usage, while Reference > counting operates on the mentioned 30ms. Is that correct? > > > > Links: > > http://www.adobe.com/devnet/flashplayer/articles/garbage_collection.html <http://www.adobe.com/devnet/flashplayer/articles/garbage_collection.htm l> > > ("some point in the future") > > http://techpolesen.blogspot.com/2007/11/avm2-vs-jvm-and-actionscript3.ht <http://techpolesen.blogspot.com/2007/11/avm2-vs-jvm-and-actionscript3.h t> > ml > > ("30ms time slice") > > > > Michael Krotscheck > > Senior Developer > > > RESOURCE INTERACTIVE > > <http://www.resource.com/ <http://www.resource.com/> > www.resource.com <http://www.resource.com <http://www.resource.com> > > > [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > > __________________________________________________________ > ____ > This email and any of its attachments may contain Resource Interactive > proprietary information, which is privileged, confidential and may be > subject to copyright or other intellectual property rights belonging to > Resource Interactive. This email is intended solely for the use of the > individual or entity to which it is addressed. If you are not the > intended recipient of this email, you are hereby notified that any > dissemination, distribution, copying or action taken in relation to the > contents of and attachments to this email is strictly prohibited and may > be unlawful. If you have received this email in error, please notify the > sender immediately and permanently delete the original and any copy of > this email and any printout. >
