Date: Tue, 28 Nov 2017 16:54:58 +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-N24qkEJc0r@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 #20 from Guido Falsi <madpilot@FreeBSD.org> --- (In reply to rozhuk.im from comment #19) > Dont waste your time to ugly kqueue() fam backend in glib, you cant fix t= his > crap by simple patches. > Kqueue based fam was broken and disabled (in ports) over year and upstream > do nothing. >=20 > Forget about about it and use libinotify or my patch: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214338 > it works fine: no crashes, no heavy cpu usage. At present the glib20 port does not include an option to use inotify or your patch. My patch is a simple incremental fix, which requires only importing upstream bits. (I'm going to update the patch shortly removing my code an replacing = it with code recently committed upstream) I'm not on the gnome team so I don't know which solution they will import in the tree, but I don't think diverging from upstream is accounted as an opti= on. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-199872-6497-N24qkEJc0r>