Fatal error ("!m_dirtyTracks-contains(trackId)")

Reported by toomuch on 2010-12-21
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mixxx
High
RJ Ryan
1.8
High
RJ Ryan

Bug Description

Hey, don't know if it is really a bug, cause I closed Mixxx when two tracks were playing.

I got this message:

ASSERT: "!m_dirtyTracks-contains(trackId)" in file src\library\dao\trackdao.cpp, line 103

Maybe this helps anyway.

RJ Ryan (rryan) wrote :

Hey toomuch,

What version of Mixxx? This shouldn't be an assertion in Mixxx 1.8.2 or Mixxx 1.9.0 beta1.

Thanks,
RJ Ryan

toomuch (toomuch) wrote :

Sorry for not mentioning.

Mixxx 1.8.2 x64 (on a Win7 x64 system).

Josh Vickerson (jpv41193) wrote :

I run into this as well every time I close Mixxx, and it also happens when I've used it for roughly an hour or so.

I'm using 1.8.2 on Vista Home Premium (32-bit, service pack 2)

toomuch (toomuch) wrote :

On 26th December I used Mixxx at a private house party with friends and Mixxx came up with this error THREE times. The current song played on until I pressed "OK". But there was no possibility to interact with it, so I had to restart Mixxx. This caused a few BUUUHHHHHs. :(

(You can also see, that Mixxx messes up the tag info sometimes: Ugly Duckling)

RJ Ryan (rryan) wrote :

I'm actually kind of shocked that this is happening in 1.8.2. I specifically removed the line of code that causes this from MIxxx 1.8.2.

RJ Ryan (rryan) wrote :

To whoever packaged the 1.8.2 Windows builds, can you verify that you packaged r2693 ?

No, r2682 was packaged. I could've sworn that was the current tip at the time I made the packages, unless I forgot to update. :S

RJ Ryan (rryan) wrote :

Well, that explains it :). Then this is fixed in the 1.8.x branch, but I don't believe we'll ever do a 1.8.3 release. This bug should be fixed with the 1.9.0 beta, then.

Thanks,
RJ

Changed in mixxx:
status: New → Fix Committed
assignee: nobody → RJ Ryan (rryan)
importance: Undecided → High

Should I repackage 1.8.2? (The only problem with doing it now is that I have to bzr update, then bzr revert to the current release182 tag, but bzr revno still shows the latest.)

On Mon, Jan 3, 2011 at 1:30 AM, Sean M. Pappalardo
<email address hidden> wrote:
> Should I repackage 1.8.2? (The only problem with doing it now is that I
> have to bzr update, then bzr revert to the current release182 tag, but
> bzr revno still shows the latest.)

Can you package up a 1.8.3 for Windows as soon as you can?

Thanks,
Albert

>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/693206
>
> Title:
>  Fatal error ("!m_dirtyTracks-contains(trackId)")
>

Dan Hughes (dan-hughes) wrote :

same problem, but it only affects me when i am exiting the program (regardless of if i click the red X or do File -> exit). It doesnt happen every time, maybe around 50-70%. if the bug occurs i lose all the changes i have made: tracks added to crates, playlists, cue points added, etc.

appreciate the hard work, mixxx team (:

RJ Ryan (rryan) on 2012-05-13
Changed in mixxx:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers