[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Change by Pablo Galindo Salgado : -- keywords: +patch nosy: +pablogsal nosy_count: 8.0 -> 9.0 pull_requests: +23297 stage: -> patch review pull_request: https://github.com/python/cpython/pull/24510 ___ Python tracker

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Change by Irit Katriel : -- Removed message: https://bugs.python.org/msg386839 ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Change by Irit Katriel : -- Removed message: https://bugs.python.org/msg386840 ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Irit Katriel added the comment: Still happening in 3.10: Python 3.10.0a5+ (heads/master:bf2e7e55d7, Feb 11 2021, 23:09:25) [MSC v.1928 64 bit (AMD64)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import gc >>> TAG = object() >>> >>> def monitor(): ...

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Irit Katriel added the comment: oops, wrong ticket. Sorry about the noise. -- status: pending -> open ___ Python tracker ___ ___ Py

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Irit Katriel added the comment: Is there anything left to do here? Looks like a 3rd party issue. -- nosy: +iritkatriel status: open -> pending ___ Python tracker ___ _

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Antoine Pitrou added the comment: What is tracd doing? This issue should only appear when calling one of the debugging functions in the gc module, AFAICT. -- ___ Python tracker

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

lkraav added the comment: I may be seeing this running tracd-1.1.2b1 on python 2.7.7 http://trac.edgewall.org/ticket/11772 -- versions: +Python 2.7 ___ Python tracker ___ __

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Changes by lkraav : -- nosy: +lkraav ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/ma

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Antoine Pitrou added the comment: > Are there any guidelines on when GIL should be released? The GIL should be released: - for CPU-heavy external functions (e.g. compression, cryptography) - for external functions which wait for I/O > Re PyTuple_SET_ITEM...yes that's also a possibility but it

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Pankaj D added the comment: Wondering the same thing myself, and yes sqlite3_column_type() by itself doesn't seem expensive. I assumed in general it was to allow more responsiveness for apps with huge number of columns (i.e. large tuple size). But we have about 20-25 columns and so I was g

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Antoine Pitrou added the comment: I wonder why _pysqlite_fetch_one_row() releases the GIL around sqlite3_column_type(). By its name, it doesn't sound like an expensive function. Another workaround would be to call PyTuple_SET_ITEM instead of PyTuple_SetItem. -- components: +Extension

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Amaury Forgeot d'Arc added the comment: Thanks for the analysis! This is quite similar to issue793822: gc.get_referrers() can access unfinished tuples. The difference here is that what breaks is not the monitoring tool, but the "main" program! Here is a simple script inspired from the origin

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Pankaj D added the comment: I believe I have found the root-cause for this issue. It is occurring due to the use of the garbage collector in another “memMonitor” thread (we run it periodically to get stats on objects, track mem leaks, etc). Since _pysqlite_fetch_one_row() releases the GI

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Pankaj D added the comment: sorry, 2.7, 3.2 is not an option currently but I am hoping someone can provide enough info to help probe this more efficiently. There seem to be references to this issue on the web but no root-cause. -- ___ Python tracke

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Changes by Jesús Cea Avión : -- components: -Cross-Build ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

Jesús Cea Avión added the comment: Could you possibly reproduce this in 2.7, 3.2 and/or "default" (future 3.3)?. Python 2.6 support is over. -- components: +Cross-Build nosy: +jcea ___ Python tracker

[issue15108] ERROR: SystemError: ./../Objects/tupleobject.c:118: bad argument to internal function

New submission from Pankaj D : Hi, Sporadically, while running an sqlite3 query, the above error is seen. In order to debug, I modified Objects/tupleobject.c, PyTuple_SetItem() as follows: if (!PyTuple_Check(op) || op->ob_refcnt != 1) { Py_XDECREF(newitem);