[Bug 246313] database/py-mysqlclient sigabort with a "GC object already tracked" message
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri May 8 17:15:19 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246313
Bug ID: 246313
Summary: database/py-mysqlclient sigabort with a "GC object
already tracked" message
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs at FreeBSD.org
Reporter: jeroen.pulles at gmail.com
Hi,
The new patch from ports r529330 causes a sigabort in python.
My impression is that this happens only with a fetchmany() on a streaming
cursor, MySQLdb.cursors.SSCursor.
Without the patch the aborts don't occur.
And i'm running a single threaded application.
Here's a snippet from ktrace output:
7850 python3.7 RET recvfrom 2572/0xa0c
7850 python3.7 CALL write(0x2,0x8002c4a6c,0x14)
7850 python3.7 GIO fd 2 wrote 20 bytes
"Fatal Python error: "
7850 python3.7 RET write 20/0x14
7850 python3.7 CALL write(0x2,0x8002c0bfc,0x19)
7850 python3.7 GIO fd 2 wrote 25 bytes
"GC object already tracked"
7850 python3.7 RET write 25/0x19
7850 python3.7 CALL write(0x2,0x8007c0a97,0x1)
7850 python3.7 GIO fd 2 wrote 1 byte
"
"
7850 python3.7 RET write 1
7850 python3.7 CALL write(0x2,0x8007c0a97,0x1)
7850 python3.7 GIO fd 2 wrote 1 byte
"
"
7850 python3.7 RET write 1
7850 python3.7 CALL write(0x2,0x8002c4af3,0x11)
7850 python3.7 GIO fd 2 wrote 17 bytes
"Current thread 0x"
7850 python3.7 RET write 17/0x11
7850 python3.7 CALL write(0x2,0x7fffdfff5600,0x10)
7850 python3.7 GIO fd 2 wrote 16 bytes
"00000008072ebf00"
7850 python3.7 RET write 16/0x10
7850 python3.7 CALL write(0x2,0x8002bf3ad,0x1b)
7850 python3.7 GIO fd 2 wrote 27 bytes
" (most recent call first):
"
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list