DEBUG ASSERT: "hintFrameCount >= 0" in function void CachingReader::hintAndMaybeWake(const HintVector&) at src/engine/cachingreader/cachingreader.cpp:535

Bug #1946759 reported by Jan Holthuis
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Committed
High
Jan Holthuis

Bug Description

When setting a beatloop in front of the actual track (i.e. so that the end of the loop is before the first audio frame), the following debug assertion will be triggered:

    DEBUG ASSERT: "hintFrameCount >= 0" in function void CachingReader::hintAndMaybeWake(const HintVector&) at src/engine/cachingreader/cachingreader.cpp:535

Steps to reproduce:

1. Go to the beginning of the track
2. Use beatjump to go to 8 beats before the beginning of the track
3. Set a Beatloop of 4 beats
4. DEBUG_ASSERT is triggered

Tags: engine looping
Changed in mixxx:
importance: Undecided → High
tags: added: engine looping
summary: DEBUG ASSERT: "hintFrameCount >= 0" in function void
CachingReader::hintAndMaybeWake(const HintVector&) at
- /home/jan/Projects/mixxx/src/engine/cachingreader/cachingreader.cpp:535
+ src/engine/cachingreader/cachingreader.cpp:535
description: updated
Revision history for this message
Jan Holthuis (holthuis-jan) wrote :

2.3 seems to be unaffected, but I can reproduce this 100% of the time on 2.4-alpha-880-g7b22498e81.

Revision history for this message
Jan Holthuis (holthuis-jan) wrote :

Looks like the assertion was introduced by 8589930ff50fdf733c8b1333aa75548990c6e573 (#1223). In 7d96c38e93a95bb2a987b8e2676e5e1ff16f0e61 (#3081, part of 2.3) I fixed a condition where the assertion was no longer true and hintFrameCount might be 0.

It looks like `main` now also makes it possible for negative values to occur?

Revision history for this message
Jan Holthuis (holthuis-jan) wrote :

Also happens when using the loop in/out buttons instead of beatloops.

Revision history for this message
Jan Holthuis (holthuis-jan) wrote :
Changed in mixxx:
assignee: nobody → Jan Holthuis (holthuis-jan)
status: New → In Progress
milestone: none → 2.4.0
Changed in mixxx:
status: In Progress → Fix Committed
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/10556

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.