Comment 3 for bug 733376

Hmm, yes we were seeing assertions even in 1.8.0 of problems where the state
was inconsistent. At the time I trusted the track's dirty-flag because it
was marked clean, but it seems that the track should be dirty and the
TrackDAO is correct. This would result in the tracks not getting saved and
being deleted from the cache.

On Fri, Mar 11, 2011 at 11:58 AM, RAFFI TEA <email address hidden>wrote:

> I can reproduce the bug: The only thing I can find in the log is:
>
> WARNING: Inconsistent state in TrackDAO. Track is clean while TrackDAO
> thinks it is dirty. Correcting
>
> rryan: Could that be the problem?
>
> ** Changed in: mixxx
> Importance: Critical => High
>
> ** Changed in: mixxx
> Milestone: None => 1.9.1
>
> --
> You received this bug notification because you are subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/733376
>
> Title:
> Track Cache does not Save to Database
>