From owner-freebsd-python@freebsd.org Thu Apr 29 18:03:25 2021 Return-Path: Delivered-To: freebsd-python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EB23D63261D for ; Thu, 29 Apr 2021 18:03:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4FWNf566pvz4ty6 for ; Thu, 29 Apr 2021 18:03:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id D20B563254B; Thu, 29 Apr 2021 18:03:25 +0000 (UTC) Delivered-To: python@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D1D3F6325B5 for ; Thu, 29 Apr 2021 18:03:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FWNf55VKMz4thL for ; Thu, 29 Apr 2021 18:03:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id AC2F81ED69 for ; Thu, 29 Apr 2021 18:03:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 13TI3PHk094533 for ; Thu, 29 Apr 2021 18:03:25 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 13TI3PVI094532 for python@FreeBSD.org; Thu, 29 Apr 2021 18:03:25 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 255445] lang/python 3.8/3.9 SIGSEV core dumps in libthr TrueNAS Date: Thu, 29 Apr 2021 18:03:25 +0000 X-Bugzilla-Reason: 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: crash, needs-patch, needs-qa X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: yocalebo@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: python@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? maintainer-feedback? X-Bugzilla-Changed-Fields: 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-python@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Apr 2021 18:03:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255445 --- Comment #13 from yocalebo@gmail.com --- Maybe some progress....not sure but I'm cautiously optimistic. I analyzed 7 core dumps again to see if I spotted anything interesting. 6 of them were py3.8 and 1 was py3.9. 100% of them have a common pattern. The threads *tstate has lxml.etree._ParserDictionaryContext in the frames. Either the thread that w= as on CPU when it core dumped or some other thread. Since this is seemingly me= mory corruption, lxml has become my suspect since it uses it's own C bindings for the libxml2 and libxslt libraries. I've instrumented a somewhat complicated script that daemonizes, creates a concurrent.futures._base.Executor class and calls methods that use lxml lib= rary to parse geom xml information in a while true loop. Am I looking at a red herring?? Idk but this grabbed my attention so I'm running the script to see if it'll tickle the problem. Maybe the version of py-lxml we're using has a subtle issue with py3.8+. (Queue my overly dramat= ic rant about py3.8 changes to PyGC_Head struct.) --=20 You are receiving this mail because: You are the assignee for the bug.=