> It's been 2 days and no-one has got back to me on this.
I am really sorry for that, vacation...
There are no limits. Neutron is flushing every 1000 tracks to the database (otherwise to much RAM will be taken to keep all information) and thus you see 48k tracks scanned.
I suspect that there is some file or folder which can't be processed by Neutron and it is dropping the scanning process.
When you are scanning Neutron is showing the progress, is it possible to see on which folder it is getting stuck? If yes, then try creating source to just that folder and check if it was scanned ok, if not then I would appreciate having its files, or just file (if single file can break the process) for analysis and workaround development.
If you prefer we can move discussion to e-mails for more operative replies: firstname.lastname@example.org
. The reason of the bug will be posted here anyway.