I guess there's some deterministic behaviour in it: If the search for new and changed media files finds someting added/changed then the scan doesn't end. It's finished and doesn't need any CPU, it logs no errors. It simply forgets to unlock the database and tell the rest of the squeezeboxserver that it has finished. So I have to abort the scan and start it again. Then it doesn't find something new and works as expected.
It there are no changes in the media collection the scan ends correctly in the first run.
So I guess there is something wrong in the "scan has finished"-notification code.
It there are no changes in the media collection the scan ends correctly in the first run.
So I guess there is something wrong in the "scan has finished"-notification code.