CrystalGipsy
Including for me! You may also remember contributing to that thread, thanks.
For some time I was a little despondent because support became… ‘slow’; it seemed as though there is/was a persistent bug which could or would not be fixed.
What I experienced looked very similar to what you are experiencing, and have experienced. I’m sorry.
None of the suggestions kindly offered by fellow posters worked. Or at least, not permanently - as is your case, alas 
.
In the end - as a matter of fact as RoonLabs tech support had said all along - I did this (as advised) and they did find (against what to me looked liked all the odds) a corrupt file. I deleted and replaced it, and have not looked back.
All I can really conclude from that is that - at least in my case - a definitely corrupt file had indeed been the cause. It may be different in other circumstance, may it not?
I wonder if it’s now time - since this does keep cropping up (although who knows how widespread it actually is, across all users) - to ‘lobby’ for a way that users can test the integrity of their databases (over and above Settings > Library > Library maintenance > Clean up Library for deleted objects, which in itself may be a little opaque in that folders are left?) so that corrupt files can be detected and indicated to the user.
I believe an FAQ would also be useful which made clear once and for all:
- whether the point in x tracks of y in the library really indicates exactly where the stall (possibly corresponding to a corrupt file) is; that is: if it stalls on, say, 32519/32521, as in your case, is that really three from the very ‘end’; or three from the end of a previously un-scanned/not-analysed subset etc
- whether, once this corrupt file (as always - assuming that a corrupt file is the cause) is replaced, does a subsequent analysis always cover the entire library
- what constitutes ‘corruption’ (CRC errors, top-bit-set characters in filenames, hidden characters etc): the file identified in my case passed all other tests (known to me) - e.g. in Yate; and otherwise played perfectly - including in Roon.
If I can help in any way with your troubleshooting, @CrystalGipsy, please do say!