Bug 2902 – Exiting slimserver still leaves process slim.exe around

Bug 2902 - Exiting slimserver still leaves process slim.exe around

Summary:

Exiting slimserver still leaves process slim.exe around

Status:	RESOLVED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Windows Service
Version:	6.2.2
Platform:	PC Windows XP

Importance:	P3 normal (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-01-30 19:37 UTC by Mark
Modified:	2008-09-15 14:38 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Mark 2006-01-30 19:37:32 UTC

If I exit slimserver (right click on icon in the notification area) and say exit slimserver, slimserver exits (the icon goes away) but when I check my list of active processes I still see slim.exe running.

Comment 1 Jim McAtee 2006-02-03 14:45:00 UTC

This is the correct behavior.  The system tray program (slimtray.exe) is not SlimServer - they're separate programs.  The tray icon progam is only a convenient means of controlling SlimServer.

The slim.exe process is SlimServer, which runs as a service on Windows.   When you select 'Exit' on the tray icon, you're exiting only from the system tray program.  You can, however, use the menu items that the tray icon presents to stop and start SlimServer itself.  If you wanted to stop SlimServer and then get rid of the tray icon, first click 'Stop SlimServer', then click 'Exit'.  Better yet, just use 'Stop SlimServer' and leave the tray icon running (it's a small program) so that you can later start up SlimServer when needed.

Comment 2 Blackketter Dean 2006-04-23 21:19:54 UTC

Hm, I'm looking at a bunch of tool tray menus and they all say exit to close the tool tray app, as opposed to stopping the corresponding service/server/etc.
I'm going to close this, but if you have a better recommendation for improving the string (possibly Microsoft recommended language) please reopen with details.