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

Dispose Track::refreshCoverImageDigest() reading covers from the main thread #4904

Merged
merged 1 commit into from
Aug 21, 2022

Conversation

daschuer
Copy link
Member

This fixes https://bugs.launchpad.net/mixxx/+bug/1905124

After a cover is read by the CoverArtDelegate via a worker thread, it tries to update the Cover Image Digest via a Track object. During creation of this Track object, the cover is read again this time from the main thread, creating the scrolling issue.

When the cover is read by widgets via an existing Track object, the CoverArtCache will update the Track object in the worker thread. There is also no need for a cover lookup in the main thread when creating the Track.

… thread.

This fixes https://bugs.launchpad.net/mixxx/+bug/1905124

After a cover is read by the CoverArtDelegate via a worker thread, it tries to update the Cover Image Digest via a Track object. During creation of this Track object, the cover is read again this time from the main thread, creating the scrolling issue.
@daschuer daschuer added this to the 2.4.0 milestone Aug 20, 2022
Copy link
Contributor

@uklotzde uklotzde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose the lazy and incremental migration of legacy cover image hashes will now be ineffective. After checking again the code in TrackDAO indeed seems to be redundant.

@daschuer
Copy link
Member Author

Thank you for checking this PR.
Since @uklotzde has surrendered his commit rights, some team member needs to review and commit.

Copy link
Member

@Swiftb0y Swiftb0y left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your explanation seems plausible and I trust @uklotzde's conclusion since they are most familiar with the code in question.

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

Successfully merging this pull request may close these issues.

3 participants