Bugzilla – Bug 5731
Starting and stopping SS7 spawns 2 scanner.exe processes
Last modified: 2009-08-31 05:58:19 UTC
I just installed the latest nightly (10/8/07) this afternoon, and SS7 started to rescan my music library as normal. I stopped and restarted ss7 in order to install some plugins and noticed that I now had two scanner.exe's running. I rebooted and repeated the process, and after stopping and restarting SS7 I again had 2 instances of scanner.exe running. Needless to say this slowed my system down a lot more than just one scanner.exe.
Are you able to reproduce this? I just tried on a fresh virtual image and I wasn't able to. Do you have a very large music collection?
I was able to produce it that day, even after a reboot but I have not tried since. Ya it's huge... \\10.0.3.91\media 25,873 songs Mike
If the db has no tracks, the scanner will start when SC starts up. Killing SC will not kill a running scanner process. I expect the launched scan hadn't yet done any periodic commit when the service was restarted, thus a new process launched. --debug scan.import at the command line will give a better idea of what caused the scan to trigger. It might be possible to kill the scanner process on shutdown, as part of the cleanup() routine. Although, not sure if that's the right thing to do versus perhaps trying to detect another scanner process before starting a new one. In most cases, the db should have an isScanning flag that does this. Not sure why this would be missed.
This shouldn't happen any more. Feel free to re-open if you still see this in 7.3.3 or later.