| System is running out of GDI-handles [message #454675] |
Wed, 27 April 2005 06:20  |
Eclipse User |
|
|
|
Originally posted by: michael.schreyer.chello.at
Hi everybody,
My app is running as eclipse3.0/3.1 plugin with Java 1.4/1.5 under
Win XP Prof., using SWT and JDT.
Task manager shows that the app consumes more and more GDI-handles
while opening/closing/refreshing TableViewers, ViewParts, etc. until
nothing is left for the system.
The number of GDI-handles also rises if a TableViewer etc. is closed
although dispose() has been called :(
The number of graphical objects (images) remains constant (sleak tells
me so), like memory consumption does.
The problem seems to be in the refresh() method.
Any idea? Thank you very much....
lg Mike
|
|
|
| Re: System is running out of GDI-handles [message #454686 is a reply to message #454675] |
Wed, 27 April 2005 09:40  |
| Eclipse User |
|
|
|
You could try posting this on eclipse.platform. The refresh() method is not
part of SWT.
"Michael Schreyer" <michael.schreyer@chello.at> wrote in message
news:3apu615908pspqjg1bfq06pll1prhgjhi0@4ax.com...
> Hi everybody,
>
> My app is running as eclipse3.0/3.1 plugin with Java 1.4/1.5 under
> Win XP Prof., using SWT and JDT.
> Task manager shows that the app consumes more and more GDI-handles
> while opening/closing/refreshing TableViewers, ViewParts, etc. until
> nothing is left for the system.
> The number of GDI-handles also rises if a TableViewer etc. is closed
> although dispose() has been called :(
> The number of graphical objects (images) remains constant (sleak tells
> me so), like memory consumption does.
> The problem seems to be in the refresh() method.
>
> Any idea? Thank you very much....
>
> lg Mike
|
|
|
Powered by
FUDForum. Page generated in 0.03416 seconds
Home