basically the title.
- start jriver media center 32 for windows.
- it is configured to be a networked media server as well
- configuration was performed via automation on update from v31
- start task manager, open the details tab, watch the entry for "Media Center 32.exe"
- exit jriver media center 32, either file->exit or the X button or alt-f4
- continue watching the task manager detail entry for "Media Center 32.exe".... forever.
- selecting "analyze wait chain" on the process yields a dialog with "one or more threads of media center 32.exe are waiting to finish network i/o", then a list of thread ids and pids.
- the hwnd window handle of the application is still valid and can be searched for using various normal windows calls. attempting to give the window focus (or anything, really) fails with the appropriate windows error codes for attempting to interact or set properties on a window that is either not finished being constructed or killed.
- starting jriver when the previous instance is in this state seems to work just fine... but the old process is not killed, there aren't duplicate processes, and the PID is the same for the newly restarted app
- killing the process manually then starting jriver works as expected, the new instance of the Media Center 32.exe process getting a new PID.
- exiting this new instance brings us back to the start with a zombie-ish process in task manager and a sort-of undead hwnd and PID.
please fix this as it's making automating certain tasks (especially those where jriver is brought to the front and given focus if it is running, or is started first if it is not running).
thank you so very much!
i happen to be a system programmer with a lot of c/c++/asm/debugging and all that under my belt, so if i can be of assistance hunting this one down, please let me know.
Author
Topic: Media Center 32.exe process never ends despite exiting the app (Read 465 times)