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

100% CPU usage when length column shown #2030

Closed
qwence opened this Issue Sep 11, 2016 · 3 comments

Comments

Projects
None yet
2 participants
@qwence
Contributor

qwence commented Sep 11, 2016

I've bisected the following issue to commit 295cc6d (and checked that the bug is not present when this commit is reverted).

When using the following minimal config

[settings]
columns = artist,composer,title,~#track,album,~#length

[memory]
column_expands = artist,0,composer,0,title,0,album,0

I get 100% CPU usage if (1) I'm using the "search library" view, and (2) the "length" column is fully visible (i.e. not squished horizontally by weird column widths). I can delete the last line in the config and this doesn't happen, but after playing with the column widths a little bit a line like this will be automatically inserted in my config, and on next startup, the issue happens again.

@lazka

This comment has been minimized.

Member

lazka commented Sep 11, 2016

Thanks. Which distro/version?

@lazka lazka added the bug label Sep 11, 2016

@lazka

This comment has been minimized.

Member

lazka commented Sep 11, 2016

Never mind. I can reproduce using your config.

@lazka lazka added this to the 3.7.1 milestone Sep 11, 2016

@lazka lazka closed this in a626770 Sep 11, 2016

@lazka

This comment has been minimized.

Member

lazka commented Sep 11, 2016

The workaround is to right click > "Expand column" on at least one other column in the list.

lazka added a commit that referenced this issue Sep 25, 2016

songlistcolumns: only queue_resize() a fixed width column in case the…
… width has changed. Fixes #2030

Fixes 100% CPU in case there are no expanding columns besides the fixed width one.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment