https://bugs.kde.org/show_bug.cgi?id=423818
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDSINFO |REPORTED
Component|general |general
Resolution|WAITINGFORINFO |---
Assignee|dolphin-bugs-n...@kde.org |mp...@kde.org
Summary|After some time no kde |KDirWatch's useFam loops
|application cant open, to |indefinitely (actual fam,
|many open files |not gamin)
Version|20.04.2 |unspecified
CC| |kdelibs-b...@kde.org
Product|dolphin |frameworks-kcoreaddons
--- Comment #11 from Harald Sitter <sit...@kde.org> ---
Thanks. Unfortunately I can't reproduce this.
Given the backtrace what appears to happen is that since inotify is not
functional, because we've exhausted the inotify instance cap, the file
monitoring will fall back to a different system called FAM and that has a loop
that has potential to never exit it looks like. A user needs to manually
install the FAM daemon to actually cause this behavior though, at least on
neon.
> do {
> famEventReceived();
> if (startedFAMMonitor && !e->m_famReportedSeen) {
> // 50 is ~half the time it takes to setup a watch. If gamin's latency
> // gets better, this can be reduced.
> QThread::msleep(50);
> }
> } while (startedFAMMonitor &&!e->m_famReportedSeen);
^ if m_famReportedSeen is never true, that loop never terminates. I'm not quite
sure why that would happen but in any event there ought to be a cap on how long
we are willing to wait which should then solve the problem that apps deadlock.
Moving bug to correct product.
--
You are receiving this mail because:
You are watching all bug changes.
