[Webkit-unassigned] [Bug 118567] [ATK] Leak: AtkRelationSet is not freed

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 12 01:53:04 PDT 2013


Mario Sanchez Prada <mario at webkit.org> changed:

           What    |Removed                     |Added
                 CC|                            |mario at webkit.org

--- Comment #2 from Mario Sanchez Prada <mario at webkit.org>  2013-07-12 01:55:06 PST ---
(In reply to comment #1)
> This seems to happen because the reference count of the target of the 
> AtkRelation (an AtkObject) increases as result of caching.

Yes, that is my guess as well. Since the memory allocated in this malloc happens because of being the first call to g_object_weak_ref() over that AtkRelation object (and not just because it should happen every time you call g_object_weark_ref()), that memory can't be released at the very same (future) moment when you call g_object_weak_unref(), since that might be causing problems.

Instead, that memory will be released when that AtkRelation object's ref count gets to zero, by means of the g_datalist_clear_data() function, which we double-checked it's what's will happen

So the point is why the object's ref_count is not getting down to zero, and I agree with Brian that probably is because of one cache retaining that object alive. Question is whether that cache is AXObjectCache, the cache in the Atk bridge or something else, and whether that's a problem (design issue in those caches?) or not.

Thus, let's keep this bug open since it will help remind us that there's something here, probably related to caches, that might require further investigation.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list