web stats

Mirth Connect

[Mirth Administrator] Java Runtime Environment (JRE) - javaw.exe still in memory after stopping Mirth Administrator

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.6.1
  • Fix Version/s: 1.7.1
  • Component/s: Administrator
  • Labels:
    None
  • Environment:
    Windows XP SP2
    Java 1.6.0 (build 1.6.0_03b-05)
    Mirth 1.6.1
  • Operating System:
    Windows XP

Description

After using Mirth Administrator, when you stop it, the javaw.exe is not killed properly ; it is still in memory.
So if you run again Mirth Administrator, it uses a new instance of javaw.exe ... using again a new part of our memory ...
After a day if you use 10 time Mirth Administrator, you've 10 javaw.exe still in memory.

have to kill them manually ...

Is there something to change in the method of exiting in Mirth Administrator or is it Java not doing is job ?

Thanks for replies

Activity

Hide
Curt Welch added a comment -
I've noticed this issues as well. I found that it only happens if you shut down the Mirth Administrator using the "Exit" button on the login-screen. If you shut it down using the window close X button, it correclty exits the javaw.exe. So as a simple work around, always exit using the window close button instead of the Exit button on the login screen.

I suspect this is just a problem of the action performed code for the Exit button doing a window close instead of a System.exit(). The javavm will not exit once you start the UI event thread running by creating the first window. It must do a full System.exit() of the vm to make it shut down correctly.

Curt Welch
cwelch@vecna.com
Show
Curt Welch added a comment - I've noticed this issues as well. I found that it only happens if you shut down the Mirth Administrator using the "Exit" button on the login-screen. If you shut it down using the window close X button, it correclty exits the javaw.exe. So as a simple work around, always exit using the window close button instead of the Exit button on the login screen. I suspect this is just a problem of the action performed code for the Exit button doing a window close instead of a System.exit(). The javavm will not exit once you start the UI event thread running by creating the first window. It must do a full System.exit() of the vm to make it shut down correctly. Curt Welch cwelch@vecna.com
Hide
Jacob Brauer added a comment -
Fixed close action of the LoginPanel so it closes the process.
Show
Jacob Brauer added a comment - Fixed close action of the LoginPanel so it closes the process.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: