9.0.2/Pi3b+: freeze when scanning library for the first time

[Iacov]

hey

as a continuation of (9.0.2) moOde always crashes when i try to scan my library (9) (moodeaudio.org)

i think i can narrow it down to two possible reasons for my issue:
either a defective sd card or a ram issue when scanning the library

what i can not rule out: that i have outliers within my library with unusual large cover images embedded

what i have observed: when the 7" pi display is activated and the GUI is running, it takes up more than 400mb of my 900mb ram. if it is off, moode only uses roughly 150mb
the library scan finished successfully after switching to usb boot (thus "removing" the possibly faulty sandisk sdhc card) and leaving the GUI off for the scan

summary:
what did not work: installing fresh 9.0.2, setting everything up, including the display GUI and after that scanning the library -> freeze
what worked: installing fresh 9.0.2, setting up smb connection to nas, scanning library and setting everything else up after the initial scan

for now i see my issue as resolved (as i'm sticking to leaving the gui off for the initial scan)
but i wanted to write down my suspicion - maybe only relevant to my library-outliers

[Tim Curtis]

Interesting. How many tracks in your collection?

[Iacov]

Interesting. How many tracks in your collection?

very roughly 6000

I forgot one important detail in my post above: the very same library could be scanned with moode 8.x without an issue and without any of the steps below

there were bad files (flacs without meta data or files with 7mb cover images embedded) which I either deleted, fixed or ignored via .mpdignore... this did not change the behavior of spontaneous freezes during a library scan... which leads me to a bad SD or maybe a ram issue (ram usage in htop was always 
very high or almost full when observed right before a freeze) 

I'm just wondering... what does a frozen RPi hint towards? my uptimekuma still could ping the pi, but I could neither ssh into it nor did the touchscreen or web ui react... 
does this symptom lean towards one hypothesis more than the other? 

after all I do not rule out that it's my hardware or library that causes this symptom. but if it could hint towards a bug, I'd be happy to offer every hint I can

[Tim Curtis]

Someone will have repro your issue and provide log data, errors or some other information that can be used to zero in on some part of the code that may be failing. We can't just go on a wild goose chase :-0

[Iacov]

Someone will have repro your issue and provide log data, errors or some other information that can be used to zero in on some part of the code that may be failing. We can't just go on a wild goose chase :-0

absolutely and I'm sorry that I cant provide more than an observation with too many variables. Just wanted to write about it, in the off chance that it's not my setup alone (edit) and maybe the hint to check the SD card or leave the gui off for the moment might help someone in a similar situation like mine

[Tim Curtis]

Of course your posts are fine and as you said someone might get a clue from them. We are in the untamed world of Bookworm now. My priority is to fix all reproducible issues before the first minor release 9.x.0

[the_bertrum]

What breed of NAS do you use? I have a similar freeze on a Pi3A+ with 9.x moode. 8.x was fine, my Pi4B+ is fine. I've bee doing a deal of investigations (need to write up some more on the thread I have about it), but I'm not coming to suspect that it's the SMB share from my Synology NAS that's the cause. If you are on SMB from a Synology too it would be another data point in support of my hypothesis.

[TheOldPresbyope]

I'm running OpenMediaVault on a HardKernel HC1 ARM-based SBC. It serves an SMB share with ca 6000 tracks of various formats.

None of the moOde 9.0.2 players I currently test---on Pi 3A+, Pi 3B+, Pi 4B, Pi 5B---have a problem adding this share to their libraries. They are all connected to my LAN via WiFi.

All in all, no evidence to suggest what might be causing the reported freeze.

The only tangible clue offered by the OP is that the freeze does not occur if the local display is disabled and that with the local display enabled he sees more memory usage...and a freeze. The amount of memory he reports seems adequate to me* but he seems to be suggesting an out-of-memory error condition might be occurring.

Were I in this situation, I'd try enabling swap (to a file) to see if the updating proceeds to completion. There are plenty of HowTo's on the subject available on the Web. NOTE- swapping to a file is inherently slow but that's the price one pays for the "extra" working memory it provides.


Just my 2-cents worth.

Regards,
Kent

*As it happens, my Pi 3B+ also has an official 7-in touch screen with the moOde local display enabled. I have no issue adding my library to it.

Querying the handy moodeutl utility:

Code:

xxx@m902pi3bp:~ $ moodeutl -m
CPU: 1.4 GHz | Load: 5% / 56C | Memory: 53% used | Disk: 35% used / 8.5G free |
...

[the_bertrum]

I have no display attached, and while the memory use does climb when scanning, the freeze comes well before the memory runs out (last time I ran that test memory was at 70% used - no swap file).

One thing these freezes are: elusive.

[Iacov]

What breed of NAS do you use?  I have a similar freeze on a Pi3A+ with 9.x moode.  8.x was fine, my Pi4B+ is fine.  I've bee doing a deal of investigations (need to write up some more on the thread I have about it), but I'm not coming to suspect that it's the SMB share from my Synology NAS that's the cause.  If you are on SMB from a Synology too it would be another data point in support of my hypothesis.

yes, dsm7 and smb

thank you @TheOldPresbyope for testing! ram was unlikely in regard that the device did not have a forced reboot or something similar that would happen on a ram overflow

could it be that I use the same  read only smb user on both my moode devices? normally this should be no problem for smb, right?

that synology/the nas could play a part can't be out ruled... yet, if you hear hoofs clacking, don't think it's zebras... the most likely cause for my issue is still my very own library/tags/files

but I don't understand why, with the same files, there is a different behavior between moode 8 and 9