| Summary: | Segfault when reached fs.inotify.max_user_watches limit | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | pwalski <przemek.walski> |
| Component: | Baloo File Daemon | Assignee: | Pinak Ahuja <pinak.ahuja> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version: | 5.35.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: | baloo_file_extr coredump | ||
This is either bug 362566 or bug 367480. *** This bug has been marked as a duplicate of bug 367480 *** |
Created attachment 106278 [details] baloo_file_extr coredump My logs contain few baloo_file_extr related segfaults (attachment) with error messages indicating reached limit of max fs watches. I do not remember changing it so it is probably a default value: $ cat /proc/sys/fs/inotify/max_user_watches 8192 Log messages like: "Failed to create watch for "/home/przemek/Projects/JS/Logger/node_modules/uglify-to-browserify/test" No space left on device" were a bit misleading - "no space left on device" was not the case.