[Digikam-devel] [digikam] [Bug 314385] Digikam crashes at startup: "Creating pipes for GWakeup: Too many open files"

[Luke]

https://bugs.kde.org/show_bug.cgi?id=314385

--- Comment #5 from Luke <lcampagn at email.unc.edu> ---
This is my interpretation: digikam is opening a large number of file handles in
multiple threads, and whichever thread crosses the 1024 limit first is the one
to crash. My understanding from some previous threads is that digikam creates
one file handle per directory to monitor for changes, and falls back to some
other mechanism when it runs out of file handles. The problem is that by
acquiring all available handles, any other part of the process may become prone
to crash. 

My understanding of this is pretty thin, though, so I'm happy to open an Ubuntu
bug as well if you think that is appropriate.

I have tried a variety of different conditions and the only way I can get
digikam to start reliably is to reduce the number of directories in my
collection. Expanding the open-file limit is one obvious solution, but as I
mentioned this just leads to other errors. 

Is there a way to disable directory monitoring, or to implement this in some
way that does not use so many handles?

-- 
You are receiving this mail because:
You are the assignee for the bug.