Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ram fills when chroma plugin is active #38

Closed
enricosan opened this issue Aug 23, 2018 · 5 comments
Closed

Ram fills when chroma plugin is active #38

enricosan opened this issue Aug 23, 2018 · 5 comments

Comments

@enricosan
Copy link

I posted about the issue here: https://groups.google.com/forum/#!topic/beets-users/rQgK1l4mIrI

Basically the ram fills when the chroma plugin is active, it doesn't fill when it's not active. Ram continues filling until beets stalls, if left for long enough all docker containers and even the unraid docker UI slows to a crawl and slowly becomes unresponsive, takes about 30mins. Ram fills to about 27GB (out of 32GB on the system) before locking up. Ram is cleared when import is cancelled or beets is restarted.

linuxserver.io

UNRAID 6.5.3

M/B: Supermicro - X9SRL-F
CPU: Intel® Xeon® CPU E5-1650 v2 @ 3.50GHz
HVM: Enabled
IOMMU: Enabled
Cache: 384 kB, 1536 kB, 12288 kB
Memory: 32 GB Multi-bit ECC (max. installable capacity 512 GB)
Network: eth0: 1000 Mb/s, full duplex, mtu 1500
eth1: not connected
Kernel: Linux 4.14.49-unRAID x86_64
OpenSSL: 1.0.2o

screen shot 2018-08-24 at 9 16 54 am

Thanks, team linuxserver.io

@jmccoy555
Copy link

Same issue here unfortunately. Disabling the chroma plugin and it works fine.

@Hobbabobba
Copy link

Hobbabobba commented Oct 27, 2018

i tried to limit the amount of RAM for the container. if i set it to 1024 MB (e.g.) it works even with the chroma plugin in auto-mode. 2048 MB (2 GB) and i never got any crash or slowdown.

@Hobbabobba
Copy link

have to correct myself: even if i limit the max RAM for the container it keeps crashing for several times.

@homerr
Copy link
Member

homerr commented Nov 19, 2018

I'm afraid this looks like it is more of an issue with the plugin than anything we're able to help with. You may find it useful to approach the developer of it, referencing this issue.

@homerr homerr closed this as completed Nov 19, 2018
@hpz937
Copy link

hpz937 commented Feb 19, 2019

I am experiencing this as well. There is an open issue for this on beets github beetbox/beets#3082
While I get this is an issue with the developer of the plugin, I feel it should be disabled by default in the linuxserver docker image until it is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants