GNOME Bugzilla – Bug 720489
crash in rate_limiter_free
Last modified: 2015-02-03 13:52:23 UTC
warning: core file may not match specified executable file.
[New LWP 1232]
[New LWP 1252]
[New LWP 1250]
[New LWP 22778]
[New LWP 1248]
warning: Could not load shared library symbols for linux-vdso.so.1.
Do you need "set solib-search-path" or "set sysroot"?
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/libexec/tracker-miner-fs'.
Program terminated with signal 11, Segmentation fault.
(Thread 0x7f1edb6b2780 (LWP 1232))
*** Bug 731817 has been marked as a duplicate of this bug. ***
See also, https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1254628 and https://bugzilla.redhat.com/show_bug.cgi?id=1043167
The cause, from what I can tell, is that g_file_monitor_emit_event is called on a separate thread when the inotify file monitor is used and so it can race with rate_limiter_timeout and emit_cb which are called from the thread-default main context. All of the backtraces I can find sugggest that two threads are busy performing GFileMonitor operations.
Specifically, there is unprotected concurrent access to the rate_limiter hash table. A simple fix would be to protect access with a mutex (possibly the one that already exists in GFileMonitor).
There is more discussion about this problem at bug 739424. I've already started working on a fix in a branch.
*** This bug has been marked as a duplicate of bug 739424 ***