06-22-2023, 11:59 AM
(06-22-2023, 11:40 AM)Sunfish Wrote: I did several tests with libraries up to 3.6TB.
1st test was with known good files, result was that the library was build properly and MoOde was working as expected. No extreme usage of memory noted.
2nd test was introducing an .mpdignore file in an already indexed folder. Again everything was working as expected. The memory usage on the other hand was jumping to about 85% of the available 0.98Gb, jumping back to less than 25% quickly.
Taking into account my first observation on files with long filenames, metadata etc, my conclusion is that the combination of long metadata fields in the audiofiles (FLAC) is causing mpdignore to choke. Recovery after this event has happened is, as far as I can tell, not possible because as soon as the MoOde Ui is opened the same event is triggered again. So the only question remaining which file is causing the problem this particular case,
"php-fpm7.4" "mpdignore", or both.
For now I removed the files causing the problems to a different location so I can enjoy listening to MoOde 64bits.
How were you able to determine which files were triggering the issue?
