[PROBLEM] PEQ + certain tracks = crash

[Sehnsucht]

@Sehnsucht 

Like @Nutul  and @the_bertrum I suspect memory when users say their player becomes sluggish.

I don't know the inner workings of the PEQ code but I'm willing to play along at home. 

I have moOde 8.3.9 installed on a Pi Zero W with Creative Technology BT-W2 USB adapter as output device. 

I have created a 2-band PEQ filter with the parameters you stated. 

I arbitrarily loaded my queue with 256 hours of music (ok, so that's more than an hour or two).

Several hours in, I've not seen memory usage exceed 50 percent as stated by moodeutl -m. (The percentage reported by moodeutl has to be taken with a grain of salt but clearly I'm not out of memory.)

If you have a specific track or two you know triggers your problem then do what Al suggested and shoot it/them to us.

Regards,
Kent

Thanks.
I'm just preparing the files now and will send you them shortly.   A few things:

htop shows 100% cpu at the point each track ends before returning to bouncing around between about 18% and 45%.  When the problem is happening badly (ie multiple lines and the pi locking up) htop shows 100% cpu but still only 240mb ram used.  Sometimes you just get a line or two of error.  When I said "crash" it just seems that way - it can be locked up for minutes so it's quicker to pull the plug but perhaps if left long enough it might always recover.  You can kill mpd (with a -9 signal) and then play another track and everything seems fine again.

There's 145meg used out of 430meg as the track plays.  I'll share two files: 3.2mb and 45mb so this isn't a memory problem.

You can click to near the end of the track to save time (one is longish) and it still goes wrong.

Edit: sent. btw I tried also sending to @the_bertrum but "PMs are disabled for this user"...