Looks good so far. I let it debug log for 6 minutes and there are no errors in the log so far.
It also already got up to 2000 scanned files in that time. I’ll let it run and see where it ends up.
Update:
It got to around 190k before the app crashed again. Restarting the scan was very quick however I think around 194k there’s something else it doesn’t like since it got stuck again. I’ll try to find out what character or file it dislikes this time later. Baby steps.
Yay, a new error emerges:
2023-10-27 20:50:11.179 Error/SmbStreamDataReader: Error opening file
java.lang.OutOfMemoryError: Failed to allocate a 56 byte allocation with 3672288 free bytes and 3586KB until OOM, target footprint 536870912, growth limit 536870912; giving up on allocation because <1% of heap free after GC.
at java.lang.reflect.Array.createMultiArray(Native Method)
at java.lang.reflect.Array.newInstance(Array.java:125)
at bu.a.a(Unknown Source:43)
at eu.b.a(Unknown Source:58)
at du.b.b(Unknown Source:3)
at sp.j.k(Unknown Source:7)
at yp.f.<init>(Unknown Source:50)
at yp.d.g(Unknown Source:27)
at yp.d.a(Unknown Source:5)
at com.google.android.gms.internal.cast.z.c(Unknown Source:60)
at yp.a.Y(Unknown Source:225)
at eq.b.i(Unknown Source:149)
at fq.l.c(Unknown Source:12)
at fq.c.a0(Unknown Source:43)
at fq.f.i(Unknown Source:18)
at hc.b.a(Unknown Source:9)
at hc.b.seek(Unknown Source:0)
at com.genimee.ktaglib.KTaglib.getMetadataFromStreamReader(Native Method)
at com.genimee.ktaglib.KTaglib.c(Unknown Source:23)
at nc.v.d(Unknown Source:1598)
at nc.v.c(Unknown Source:250)
at nc.v.b(Unknown Source:181)
at nc.e.v(Unknown Source:353)
at ir.a.o(Unknown Source:5)
at fs.i0.run(Unknown Source:109)
at tm.u6.run(Unknown Source:27)
at ls.i.run(Unknown Source:2)
at ls.a.run(Unknown Source:91)
My phone ran out of ram, did it not? Happened around 198.000 tracks. The log shows no errors prior to that one.
Not the phone, but the max memory an app can allocate yes. I would have hoped that it could handle a little more but nearly 200 000k tracks is not that bad and should covers 99% of the users.
Thanks a lot again for the tests.
Pity that it can’t do more.
With the cached entries the scanning was really fast. Far quicker than jellyfin and almost on par with musicbee which takes ~20min to rescan my library.
At least you can be fairly confident now that it won’t choke on weird characters any more.
Well this is a phone, it’s hard to handle 900 000k songs 
Not sure there’s any other app that can handle more on a phone.
True, true.
I’m still amazed that it can handle my collection as well as it does (or at all for that matter).