Clementine's monitoring of music library results in all kinds of crashes when too many file handles are open
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
clementine (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
For the past few days, I've been getting a lot of errors from clementine. Some errors are this:
pa_
LibraryBackend: unable to open database file Unable to fetch row
Sometimes, it's a gstreamer error:
GStreamer-
Both of those show up in GUI dialog boxes. Outputted to the console, I see errors like this, repeated for dozens of directories in my Music collection:
2:05:53.962 WARN unknown QFileSystemWatcher: failed to add paths: /home/(
Then when you try to play music, either the database error from above shows, the gstreamer error is shown in a dialog box, or the app just exits.
There are two things I find resolve the problem.
1. Splitting my music collection in half and putting half in one directory and half in another, then only using one directory at once. Because this solves the problem, I know that no particular file is tripping up clementine.
2. Disable the "Preferences -> Monitor the library for changes" resolves the problem entirely, regardless of the size of my music collection.
I believe that Clementine is using QFileWatcher to watch changes to my music collection, and now my music collection is large enough that this behavior causes Clementine to run out of file handles.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: clementine 1.0.1+dfsg-2ubuntu3
ProcVersionSign
Uname: Linux 3.5.0-22-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Wed Jan 30 11:59:55 2013
EcryptfsInUse: Yes
MarkForUpload: True
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=
SourcePackage: clementine
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in clementine (Ubuntu): | |
status: | New → Confirmed |
To be considered complete, a bug report should normally contain:
What version of Ubuntu are you running?
What version of the package are you using?
The actions taken to produce the problem?
Whether or not it is possible for the reporter to reproduce the bug?
The expected result of these actions?
The actual result of these actions?