Date: Thu, 17 Nov 2016 23:19:14 +0000 From: bugzilla-noreply@freebsd.org To: gnome@FreeBSD.org Subject: [Bug 214338] devel/glib20: patch: new kqueue() backend for file monitoring Message-ID: <bug-214338-6497-XNf7prYijv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-214338-6497@https.bugs.freebsd.org/bugzilla/> References: <bug-214338-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=3D214338 Vladimir Kondratyev <wulf@cicgroup.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wulf@cicgroup.ru --- Comment #1 from Vladimir Kondratyev <wulf@cicgroup.ru> --- (In reply to rozhuk.im from comment #0) > - no additional threads created Just wondering. Is it safe to call readdir() from glib worker thread contex= t? Are there any chances that glib-based application would just freeze if readdir() would take tooooo looong time to complete? I don`t know much about glib internals, that is why I am asking --=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-214338-6497-XNf7prYijv>