6th January 2008 at 9:37 am #2108
I am finally operating in a fairly controllable environment after having run Firefly casually for the past 6 months.
I updated to 1696 a couple months ago and noticed that Firefly wants all available CPU resources whether it is scanning, “idle” or streaming. (Shutting down running programs and optional services only grants Firefly the right to take even more CPU.)
Is this behavior due to a bug? Are there well-understood mitigation and troubleshooting techniques? (Should I back off to an earlier version?)
Elsewhere I saw a message asserting that problem media files can touch off this behavior. The writer recommended a trial-and-error approach to find music files that Firefly finds objectionable. Considering that I have a huge 500G music collection, this method could take me forever.
Thanks for any tips anyone can offer.6th January 2008 at 10:35 am #15754stretchParticipant
svn-1696 has a bug that kicks in when you do a rescan. The database becomes corrupted & unusable
To avoid it, you can either switch to an sqlite3 database or drop back to an older version6th January 2008 at 2:10 pm #15755
Thanks for the speedy reply. I should have indicated that I was already using sqlite3 with 1696 so I guess my best move is to step back to the next earlier strong version.7th January 2008 at 1:58 am #15756stretch wrote:svn-1696 has a bug that kicks in when you do a rescan. The database becomes corrupted & unusable
I installed over my previous installation stepping back to svn-1586. Because it kept my .conf file, I am still using sqlite3. My smart playlists were preserved. The rescan went smoothly and now current CPU usage is more reasonable.
My experience tells me that svn-1696 is unsuitable for production use. I can’t wait to see what Ron comes up with for the next major release.8th January 2008 at 6:49 am #15757
- The forum ‘Nightlies Feedback’ is closed to new topics and replies.