RE: [flexcoders] Flex 4 Profiling Question - GC Root?
Somewhere you can adjust the cut off of how many paths to root are filtered out. I don't have the UI handy right now Alex Harui Flex SDK Developer Adobe Systems Inc.http://www.adobe.com/ Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Doug McCune Sent: Thursday, June 11, 2009 5:58 PM To: flexcoders@yahoogroups.com Subject: Re: [flexcoders] Flex 4 Profiling Question - GC Root? will filter out chains that have long paths back to the root as those are less likely to be the source of a problem. I'm curious about this part about filtering out chains with very long paths. I've come across quite a few instances of loitering objects in the FB 4 profiler that don't show any back references. When you expand the reference it just lists itself and it says that it is a GC root node. But then doing some really aggressive stuff to try to free up all possible references does indded get those items collected (meaning that I don't think it can be blamed on the GC simply not running when I took my snapshot, etc). Could this be because there are filtered out chains that I'm not seeing? Is there any way to selectively turn any kind of filtering like this off? Doug
Re: [flexcoders] Flex 4 Profiling Question - GC Root?
I getcha, thx Alex -mL Alex Harui wrote: The mark and sweep starts from several places (ApplicationDomain, Stage, a few internal places in the Player, stack). Those are currently called GCRoots, although I’d push for changing it if we could come up with a better name. Often when you looked at an object in the Flex 3 profiler it had many backreferences, most of which were circular, and others that were long chains through many different objects and still were circular, or didn’t matter because the real problem was that some other object along that chain was the culprit. The Flex 4 profiler removes all circular references and then will filter out chains that have long paths back to the root as those are less likely to be the source of a problem. Alex Harui Flex SDK Developer Adobe Systems Inc. http://www.adobe.com/ Blog: http://blogs.adobe.com/aharui http://blogs.adobe.com/aharui *From:* flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] *On Behalf Of *Mark Lapasa *Sent:* Thursday, June 11, 2009 7:39 AM *To:* Flexcoders *Subject:* [flexcoders] Flex 4 Profiling Question - GC Root? I was going over the Adobe Flex 4 Feature and Migration PDF which is pretty good synopsis so far of what's new in Flex 4. Under the Profiling Enhancements section, it says you can now view all the shortest paths from the object to the garbage collector root (GC root) I understand as much as the mark sweep but what does the above exactly mean? Thx, -mL Notice of confidentiality: The information contained in this e-mail is intended only for the use of the individual or entity named above and may be confidential. Should the reader of this message not be the intended recipient, you are hereby notified that any unauthorized dissemination, distribution or reproduction of this message is strictly prohibited. If you have received this message in error, please advise the sender immediately and destroy the e-mail. Notice of confidentiality: The information contained in this e-mail is intended only for the use of the individual or entity named above and may be confidential. Should the reader of this message not be the intended recipient, you are hereby notified that any unauthorized dissemination, distribution or reproduction of this message is strictly prohibited. If you have received this message in error, please advise the sender immediately and destroy the e-mail.
RE: [flexcoders] Flex 4 Profiling Question - GC Root?
The mark and sweep starts from several places (ApplicationDomain, Stage, a few internal places in the Player, stack). Those are currently called GCRoots, although I'd push for changing it if we could come up with a better name. Often when you looked at an object in the Flex 3 profiler it had many backreferences, most of which were circular, and others that were long chains through many different objects and still were circular, or didn't matter because the real problem was that some other object along that chain was the culprit. The Flex 4 profiler removes all circular references and then will filter out chains that have long paths back to the root as those are less likely to be the source of a problem. Alex Harui Flex SDK Developer Adobe Systems Inc.http://www.adobe.com/ Blog: http://blogs.adobe.com/aharui From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On Behalf Of Mark Lapasa Sent: Thursday, June 11, 2009 7:39 AM To: Flexcoders Subject: [flexcoders] Flex 4 Profiling Question - GC Root? I was going over the Adobe Flex 4 Feature and Migration PDF which is pretty good synopsis so far of what's new in Flex 4. Under the Profiling Enhancements section, it says you can now view all the shortest paths from the object to the garbage collector root (GC root) I understand as much as the mark sweep but what does the above exactly mean? Thx, -mL Notice of confidentiality: The information contained in this e-mail is intended only for the use of the individual or entity named above and may be confidential. Should the reader of this message not be the intended recipient, you are hereby notified that any unauthorized dissemination, distribution or reproduction of this message is strictly prohibited. If you have received this message in error, please advise the sender immediately and destroy the e-mail.
Re: [flexcoders] Flex 4 Profiling Question - GC Root?
will filter out chains that have long paths back to the root as those are less likely to be the source of a problem. I'm curious about this part about filtering out chains with very long paths. I've come across quite a few instances of loitering objects in the FB 4 profiler that don't show any back references. When you expand the reference it just lists itself and it says that it is a GC root node. But then doing some really aggressive stuff to try to free up all possible references does indded get those items collected (meaning that I don't think it can be blamed on the GC simply not running when I took my snapshot, etc). Could this be because there are filtered out chains that I'm not seeing? Is there any way to selectively turn any kind of filtering like this off? Doug
