Date: Sun, 28 Jan 2018 21:26:33 +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-dDWRhkRqib@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 #35 from rozhuk.im@gmail.com --- (In reply to Guido Falsi from comment #32) Do you and gnome group understand situation!? This is not some small bug in freak port with few users. This BIG ANNOYING BUG that all users can see every day. They see that many apps is crashing and think: "whole FreeBSD is crap", bec= ause on Linux, mac and windows same does not happen so rarely. Even on windows 9= 8se explorer and apps was not crash on file operations. Is windows 98se better than FreeBSD 11 on desktop? How long you will use mac/windows and told here about some tests, right way= to apply and support patches!? As FreeBSD user on desktop I do not care about: "need tests with other port= s" and "I don't think it good to include this into ports" - just fix that cras= hes, what are you waiting for? Forget about glib legacy kqueue() FAM backend. Is is totally broken many ye= ars. Select between libinotify and my patch or let users to choose via options. Is it so difficult? This is a ticket of shame. IMHO. --=20 You are receiving this mail because: You are on the CC list for the bug. 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-dDWRhkRqib>