New GitHub issue #101139 from zooba:<br>
<hr>
<pre>
This is currently the number one crash reported through Windows Error Reporting. It appears to be something to do with a repr during finalization. I haven't dug into the actual lines of code, but the line numbers below should be accurate as of 3.11.1
<html>
<body>
<!--StartFragment-->
symbol | offset | IP | filename | line
-- | -- | -- | -- | --
0 | python311!_PyObject_VectorcallTstate | 0x0000000000000024 | pycore_call.h | 87
1 | python311!PyObject_CallOneArg | 0x0000000000000030 | call.c | 377
2 | python311!PyObject_Repr | 0x000000000000008B | object.c | 434
3 | python311!_PyEval_EvalFrameDefault | 0x0000000000007136 | ceval.c | 5506
4 | python311!_PyObject_VectorcallTstate | 0x0000000000000354 | pycore_call.h | 92
5 | python311!PyObject_CallOneArg | 0x0000000000000030 | call.c | 377
6 | python311!slot_tp_repr | 0x0000000000000039 | typeobject.c | 7559
7 | python311!PyObject_Repr | 0x000000000000008B | object.c | 434
8 | python311!_PyEval_EvalFrameDefault | 0x0000000000007136 | ceval.c | 5506
9 | python311!_PyObject_VectorcallTstate | 0x0000000000000354 | pycore_call.h | 92
10 | python311!PyObject_CallOneArg | 0x0000000000000030 | call.c | 377
11 | python311!slot_tp_finalize | 0x000000000000005F | typeobject.c | 7909
12 | python311!finalize_garbage | 0x00000000000000A5 | gcmodule.c | 980
13 | python311!gc_collect_main | 0x0000000000000143 | gcmodule.c | 1280
14 | python311!_PyGC_CollectNoFail | 0x0000000000000030 | gcmodule.c | 2111
15 | python311!finalize_modules | 0x00000000000000F0 | pylifecycle.c | 1601
16 | python311!Py_FinalizeEx | 0x00000000000000A1 | pylifecycle.c | 1839
17 | python311!Py_RunMain | 0x000000000000001A | main.c | 682
<!--EndFragment-->
</body>
</html>
</pre>
<hr>
<a href="https://github.com/python/cpython/issues/101139">View on GitHub</a>
<p>Labels: 3.11, type-crash</p>
<p>Assignee: </p>