Bug 381622 - Segfault when reached fs.inotify.max_user_watches limit
Summary: Segfault when reached fs.inotify.max_user_watches limit
Status: RESOLVED DUPLICATE of bug 367480
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.35.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-24 20:09 UTC by pwalski
Modified: 2017-07-17 20:28 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
baloo_file_extr coredump (5.62 KB, text/plain)
2017-06-24 20:09 UTC, pwalski 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description pwalski 2017-06-24 20:09:06 UTC 
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.
Comment 1 Christoph Feck 2017-07-17 20:28:32 UTC 
This is either bug 362566 or bug 367480.

*** This bug has been marked as a duplicate of bug 367480 ***