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

Playing a duplicate track with same location crashes Mixxx with debug assert #13140

Open
fwcd opened this issue Apr 20, 2024 · 1 comment
Open
Labels

Comments

@fwcd
Copy link
Member

fwcd commented Apr 20, 2024

Bug Description

It seems that playing one of two tracks with the same location can crash Mixxx (if debug asserts are enabled):

warning [Main] GlobalTrackCache - Found a different track for the same canonical location: requested =  TrackRef {"<path/to/my/track>","<path/to/my/track>",90208} cached =  TrackRef {"<path/to/my/track>","<path/to/my/track>",90586}
DEBUG ASSERT: "!trackId.isValid() || trackId == cacheResolver.getTrackRef().getId()" in function TrackPointer TrackDAO::getTrackById(TrackId) const at src/library/dao/trackdao.cpp:1440
zsh: abort      build-2.4/mixxx

Not sure why this duplicate track got there in the first place, but probably something worth addressing (if this constraint isn't handled at the db level).

Version

2.4 (f225751)

OS

macOS 14.4.1

@ronso0
Copy link
Member

ronso0 commented Sep 29, 2024

Not sure why this duplicate track got there in the first place, but probably something worth addressing (if this constraint isn't handled at the db level).

quoting myself from #13685
FWIW I couldn't duplicate a track with DB Browser for SQlite, it prevents that:
Error changing data: UNIQUE constraint failed: track_locations.location

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

No branches or pull requests

2 participants