Memory leak - unable to dispose of PaletteEntry images [message #228821] |
Wed, 10 January 2007 15:55 |
Eclipse User |
|
|
|
Originally posted by: kevin.21csi.com
I'm using the PaletteEntry icons in an unorthodox way and
wondering how I can get a reference to the ImageCache or clear the cache
in the edit part so I can prevent a memory leak. I use the small/large
icon as a canvas and I'm continuously setting the image descriptors of
both. The image descriptors are usually different causing a new image to
be cached each time.
Is there any plans to adopt the new JFace image cache style as suggested
in the following reply in the mailing list:
"The Palette's use of a static image cache was borrowed from
ActionContributionItem in JFace. JFace has since fixed this and uses a
global reference counting solution. There should be a bug open to clean
this up but if you can't find one open another.
-Randy"
Thanks,
Kevin
|
|
|
|
Re: Memory leak - unable to dispose of PaletteEntry images [message #228852 is a reply to message #228844] |
Wed, 10 January 2007 16:50 |
Eclipse User |
|
|
|
Originally posted by: kevin.21csi.com
I believe it is covered in the 154145 bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=154145
Anthony Hunter wrote:
> Hi Kevin,
>
> Were you able to fix a Bugzilla reference?
>
> Cheers...
> Anthony
>
> "Kevin Shallenberger" <kevin@21csi.com> wrote in message
> news:eo329a$6jr$1@utils.eclipse.org...
>> I'm using the PaletteEntry icons in an unorthodox way and
>> wondering how I can get a reference to the ImageCache or clear the cache
>> in the edit part so I can prevent a memory leak. I use the small/large
>> icon as a canvas and I'm continuously setting the image descriptors of
>> both. The image descriptors are usually different causing a new image to
>> be cached each time.
>>
>> Is there any plans to adopt the new JFace image cache style as suggested
>> in the following reply in the mailing list:
>>
>> "The Palette's use of a static image cache was borrowed from
>> ActionContributionItem in JFace. JFace has since fixed this and uses a
>> global reference counting solution. There should be a bug open to clean
>> this up but if you can't find one open another.
>>
>> -Randy"
>>
>>
>> Thanks,
>> Kevin
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03867 seconds