One other thing to point out -- the original code puts the adding of tracks
in a transaction via ScopedTransaction. Now that the adding happens over
many function calls you will need to either manually start and commit the
transaction or possibly pull the ScopedTransaction into the library scanner
and out of the DAO. (I much prefer ScopedTransaction to manually managing
the transaction because it eliminates the possibility that you've forgotten
to commit or rollback and leave the database in a bad state).
On Thu, Jun 28, 2012 at 12:09 PM, Max Linke <email address hidden>wrote:
One other thing to point out -- the original code puts the adding of tracks
in a transaction via ScopedTransaction. Now that the adding happens over
many function calls you will need to either manually start and commit the
transaction or possibly pull the ScopedTransaction into the library scanner
and out of the DAO. (I much prefer ScopedTransaction to manually managing
the transaction because it eliminates the possibility that you've forgotten
to commit or rollback and leave the database in a bad state).
On Thu, Jun 28, 2012 at 12:09 PM, Max Linke <email address hidden>wrote:
> Shame on me, I was wrong with the mutexLocker. I have to scope it in :getTrack( ) so that mixxx won't freeze. scanner_ track_dao_ v10.patch" /bugs.launchpad .net/mixxx/ +bug/801700/ +attachment/ 3206846/ +files/ library_ scanner_ track_dao_ v10.patch /bugs.launchpad .net/bugs/ 801700 /bugs.launchpad .net/mixxx/ +bug/801700/ +subscriptions
> TrackDAO:
>
> This patches uses setValue,which is indead nicer) and all functions now
> use getTrackForColumn with the reference call, I probably made an error
> earlier.
>
> ** Patch added: "library_
>
> https:/
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https:/
>
> Title:
> high memory consumption when indexing library
>
> To manage notifications about this bug go to:
> https:/
>