From owner-freebsd-gnome@freebsd.org Thu Nov 16 23:14:00 2017 Return-Path: Delivered-To: freebsd-gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2954DED13C for ; Thu, 16 Nov 2017 23:14:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 993707039F for ; Thu, 16 Nov 2017 23:14:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9724DDED13B; Thu, 16 Nov 2017 23:14:00 +0000 (UTC) Delivered-To: gnome@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96C3BDED13A for ; Thu, 16 Nov 2017 23:14:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 83F587039E for ; Thu, 16 Nov 2017 23:14:00 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id vAGNDxh0068167 for ; Thu, 16 Nov 2017 23:14:00 GMT (envelope-from bugzilla-noreply@freebsd.org) 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 Date: Thu, 16 Nov 2017 23:13:59 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: madpilot@FreeBSD.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: gnome@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? merge-quarterly? X-Bugzilla-Changed-Fields: attachments.isobsolete flagtypes.name attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Nov 2017 23:14:00 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D199872 Guido Falsi changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #186826|0 |1 is obsolete| | Attachment #186826|maintainer-approval?(gnome@ | Flags|FreeBSD.org) | Attachment #188059| |maintainer-approval?(gnome@ Flags| |FreeBSD.org) --- Comment #18 from Guido Falsi --- Created attachment 188059 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D188059&action= =3Dedit Further update glib patch I have analysed another crash, in x11-wm/xfce4-desktop this time. I've discovered a code path in the kqueue helper casing glib to exit due t= o a filed assertion. This is triggered when a kqueue NOTE_RENAME is generated on a file. The code translates it in a G_FILE_MONITOR_EVENT_MOVED and passes it to g_file_monitor_source_handle_event(), where it ends in an assertion every t= ime. I simply commented out the code causing this, so this event is actually ignored. It does not look like a problem since this code path is bound to end in a failed assertion every time, while the same file move causing this event wi= ll also generate an event for the parent directory, which is handled through a slightly different code path. My intuition is that while kqueue generates NOTE_RENAME events for single files, GIO semantics are that such events should be generated only for moves happening in watched directories, so ignoring a moved event for a file here= is actually correct. Please test this patch, I think it will fix a few more problems, but needs ample testing to make sure it's not causing problems in other areas. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=