|Re: javaw.exe keeps running in Windows [message #449333 is a reply to message #449330]
||Fri, 21 January 2005 21:54
| Bill Ewing
Registered: July 2009
> I think it happens when you do not dispose display object.
> "Bill Ewing" <email@example.com> wrote in message
>> After we run our app (under eclipse or standalone), an instance of
>> javaw.exe (Windows' virtual machince launcher) remains in the Task
>> After coding and debugging for an hour, there's lots of them. Eventually,
>> system problems occur.
>> This problem is very noticeable when we cannot delete or rename an
>> application-related file because it is "in use." Using Task Manager to
>> kill off the javaw.exe remedies this problem. However, one of the
>> javaw.exe's was used to launch eclipse, so killing it immediately takes
>> down eclipse (with no file saves).
>> Our current hypothesis is that we are failing to dispose() of resources
>> (probably a nonstandard Color object obtained from a GC).
>> Does this sound like the right theory and does anybody have a similar
>> experience they'd like to share?
Hi Bahram. Excellent idea, thank you for taking the time to share it.
We went through our code and checked every use of Display, but still have
((On this subject, would everyone agree that in general, once your app is
up and running, it is a good idea to use the static method
"Display.getCurrent()" when you need a reference to the display?))
Powered by FUDForum
. Page generated in 0.02721 seconds