Many people (generally developers) were experiencing database-is-locked
error messages and crashes because of the way we were listing Playlists on
the sidebar. We were using a QSqlTableModel which if there are more rows
than it fetches by default in the result set then it keeps a lock on the
database. Since we were never fetching more results from it the lock was
always on once the playlist table reached a certain size. The setlog
feature triggered this because it created a new playlist every time you
start Mixxx. Fixing this issue got rid of the database-is-locked issues
that were plaguing us over the summer.
On Wed, Nov 21, 2012 at 4:19 AM, Max Linke <email address hidden>wrote:
Many people (generally developers) were experiencing database-is-locked
error messages and crashes because of the way we were listing Playlists on
the sidebar. We were using a QSqlTableModel which if there are more rows
than it fetches by default in the result set then it keeps a lock on the
database. Since we were never fetching more results from it the lock was
always on once the playlist table reached a certain size. The setlog
feature triggered this because it created a new playlist every time you
start Mixxx. Fixing this issue got rid of the database-is-locked issues
that were plaguing us over the summer.
On Wed, Nov 21, 2012 at 4:19 AM, Max Linke <email address hidden>wrote:
> Which locks are you referring to? /bugs.launchpad .net/bugs/ 1051106 /bugs.launchpad .net/mixxx/ +bug/1051106/ +subscriptions
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https:/
>
> Title:
> libraryscanner blocks the library for other transactions
>
> To manage notifications about this bug go to:
> https:/
>