[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Oxygen] [Bug 304381] X-resource leak when using Eclipse and oxygen-gtk
From:       Hugo Pereira Da Costa <hugo.pereira () free ! fr>
Date:       2013-03-01 9:04:23
Message-ID: bug-304381-17878-qdhxV2ofwp () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=304381

--- Comment #8 from Hugo Pereira Da Costa <hugo.pereira@free.fr> ---
@Gael 
thanks for the numbers.
20 thousands pixmaps is definitely too much.
Now I'm not sure they are allocated by us. Will check the caches again ... 
Also: which version of oxygen-gtk do you have (it is largely uncorrelated with
the version of KDE and is not shipped with KDE). 

Concerning your question "how could I help to fix this".
Ideally: use valgrind with eclipse. But 
1/ I have not succeeded to do so myself
2/ I'm not sure it is even possible due to its plugin nature and the use of
Java ... 
I've googled a bit already but with no success ...

(my concern, to be honest, is that as far as I know the same behavior is _not_
achieved with other gtk applications, running with oxygen-gtk. A lot of pixmaps
are created, but the number "saturates" to around 1000, which corresponds to
the caches being full. So that there must be something upstream (eclipse) that
triggers this behavior together with oxygen-gtk ...

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]