beet alt ballons memory, may lead to OOM

[knuurr]

Using beets-alternavives. I Installed it within docker container. I'm deploying it using docker-compose with hard limits for usage:

    deploy:
      resources:
        limits:
          # Adjust as needed
          cpus: '0.5'
          memory: '2048M'

I've discovered that running command may lead to OOM condition.
Here's part from inside of container when ran from interactive shell:

/src # beet alt 

usage: beet alt [-h] {update,list-tracks} ...
beet alt: error: the following arguments are required: {update,list-tracks}
/src # 
/src # beet alt uptade mp3-mirror
usage: beet alt [-h] {update,list-tracks} ...
beet alt: error: argument {update,list-tracks}: invalid choice: 'uptade' (choose from 'update', 'list-tracks')
/src # beet alt update mp3-mirror
     
Killed
/src # 
/src # 

Note: "Killed" occured automatically. I didn't do that manually.

This is confirmed from my Grafana output:

[geigerzaehler]

Thanks for reporting this, @knuurr. At the moment I don’t have any idea what could cause the high memory consumption. Would you mind sharing your configuration with me so I can investigate further? If you feel comfortable sharing it with me, a copy of the SQLite database with your library would also be very helpful. It’s usually named library.db and you can send it to me via email.