Sending from proper account, sorry.
On Wed, Sep 23, 2009 at 1:05 PM, Anton Muhin <ant...@google.com> wrote:
> In your case there should be not that many DOM windows objects and
> they all should survive in batches, so if I'd face such a problem, I'd
> just put a break point to see why this object got marked in the first
> place (that should be doable with simple conditional breakpoint).
>
> And just in case, Vitaly is working on leaks, so if you provide more
> details, chances are this issue is already known and being worked on.
>
> yours,
> anton.
>
> On Wed, Sep 23, 2009 at 1:47 AM, Jens Alfke <s...@google.com> wrote:
>>
>> Are there any utilities that can be used to see which native (DOM)
>> objects are being referenced by JavaScript objects, and to follow
>> references between JS objects to understand what's keeping an object
>> from being GCd?
>>
>> (I'm working on reducing Chrome memory usage. One thing I've
>> discovered is that WebCore::DOMWindow objects (and all their
>> associated object trees) are sometimes being left behind. JavaScript
>> seems to be implicated, as the problem goes away if I disable JS. So
>> something in V8 seems to be holding onto references to DOMWindows, and
>> I'd like to find out what it is.)
>>
>> Thanks!
>>
>> —Jens
>> >>
>>
>
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
