Bugzilla – Bug 1733
Browser launched from tray can come up before service has started.
Last modified: 2009-09-08 09:14:08 UTC
There should also be a 'Restart SlimServer' option in SlimTray whenever the service is currently running. I don't like the automatic launching of a browser window when the SlimServer service is started from SlimTray. On my system the browser window comes up before the service fully starts, so I receive a "The page cannot be displayed" error in the browser. In any case, it's unnecessary.
Hmm...that's weird. The browser isn't launched until we get a confirmation that the service has started. We probably won't modify the UI of SlimTray for 6.1, but I'd like to investigate the browser launch issue.
You can stop and start the service from the tray. Changing description to reflect the described bug. Vid: could this be that the service process has started, but the web interface hasn't come up yet?
Update: The problem on my system only occurs when IE is the default browser. If Firefox is the default then it displays a status bar message of "Waiting for localhost..." for several seconds and then it brings up the web page. I still contend that SlimTray shouldn't be launching a browser window after starting the service and then you won't have to worry about the issue. Or make the behavior a SlimTray pref (see Bug #1998).
Something just occurred to me. I'm using srvany.exe on Windows XP to run the Perl version of SlimServer as a service. Doing this has some idiosyncrasies. For instance, SlimServer can completely crash, but Windows still thinks that the service is running because srvany is still running. Only the Perl script (or perl.exe) launched under srvany is no longer running. This could be the reason for the browser/startup problem - srvany starts and reports back that it's running, but SlimServer hasn't yet completely started. If your testing doesn't recreate the problem with the compiled Windows service and IE, then maybe just call this one "resolved".
Ah, that explains it. Thanks.