Date: Sun, 20 Nov 2016 21:42:00 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 199872] devel/glib20 Apps using glib 2.42.2 crashing with 'pthread_mutex_lock' abort Message-ID: <bug-199872-6497-LoteUZoApQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-199872-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-199872-6497@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199872 --- Comment #13 from Vladimir Kondratyev <wulf@cicgroup.ru> --- (In reply to Tobias Kortkamp from comment #12) > I'm also unable to trigger crashes intentionally. I use inotify as gio backend for more than year w/o any issues. But this patch has one drawback - it unconditionally disables watching for = file content modifications in watched directories with removing of IN_MODIFY, IN_ATTRIB and IN_CLOSE_WRITE flags from inotify_add_watch() arguments. Right way IMO is to leave this flags for local directories and remove it for watching for network mounts and removable devices. Something similar is done for native kqueue gio backend but not for inotify: https://github.com/GNOME/glib/blob/master/gio/kqueue/kqueue-exclusions.c --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199872-6497-LoteUZoApQ>