[issue46061] Journal execution gives fatal error in Python 3.10.1

2021-12-13 Thread Ajaya Sutar 


New submission from Ajaya Sutar :

+++ General Fault Exception
+++ Invalid read from 
rsp:   74b27f8a10, rip: 7ffe704e2f93, rbp:   74b27f8ce9
rsi:0, rdi:0
rax:0, rbx:   7f, rcx:  194b6e9, rdx:   
   194b6e9
r8:   194b6db96c0, r9: 1, r10: 8000, r11:   
74b27f8a00
r12:0, r13:0, r14:  19484550e40, r15:   
 0
[ 1] 7FFE704E2F93 pylifecycle\fatal_output_debug Line 2492 +0x43   
(python310) 
[ 2] 7FFE704E3CCA pylifecycle\fatal_error Line 2734 +0x2ba 
(python310) 
[ 3] 7FFE704E3E4C pylifecycle\_Py_FatalErrorFormat Line 2784 +0xec 
(python310) 
[ 4] 7FFE704E6F52 pystate\PyThreadState_Delete Line 930 +0x52  
(python310) 
[ 5] 7FFE704E1BF9 pylifecycle\new_interpreter Line 1967 +0x269 
(python310) 
[ 6] 7FFE704E1CDF pylifecycle\Py_NewInterpreter Line 1988 +0x1f
(python310)

--
components: C API
messages: 408431
nosy: eaqrzn
priority: normal
severity: normal
status: open
title: Journal execution gives fatal error in Python 3.10.1
type: crash
versions: Python 3.10

___
Python tracker 
<https://bugs.python.org/issue46061>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46061] Journal execution gives fatal error in Python 3.10.1

2021-12-13 Thread Ajaya Sutar 


Ajaya Sutar  added the comment:

It is a simply python script. Even if you will run a simply python script 
without any content that is giving error. Just for example journal.py if we run 
it is also giving error. In python 3.8, we are able to create // create 
sub-interpreter using Py_NewInterpreter  and it is working fine. but in python 
3.10.1 it is not working fine. it is giving fatal error.

--

___
Python tracker 
<https://bugs.python.org/issue46061>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46061] GCState *gcstate = get_gc_state() gives fatal error in Python 3.10.2

2022-03-03 Thread Ajaya Sutar 


Ajaya Sutar  added the comment:

I was running one python script. At the time of python exit while calling 
Py_XDECREF(weakRefObject), it is calling giving exception in python 3.10.2. 

While debugging found  

In python 3.8.12, it is working fine with _PyRuntime.

void
PyObject_GC_Del(void *op)
{
PyGC_Head *g = AS_GC(op);
if (_PyObject_GC_IS_TRACKED(op)) {
gc_list_remove(g);
}
struct _gc_runtime_state *state = &_PyRuntime.gc;
if (state->generations[0].count > 0) {
state->generations[0].count--;
}
PyObject_FREE(g);
}

But in Python 3.10.2 it is not working with get_gc_state() giving exception. It 
seems it is memory issues. 

void
PyObject_GC_Del(void *op)
{
PyGC_Head *g = AS_GC(op);
if (_PyObject_GC_IS_TRACKED(op)) {
gc_list_remove(g);
}
GCState *gcstate = get_gc_state();
if (gcstate->generations[0].count > 0) {
gcstate->generations[0].count--;
}
PyObject_Free(g);
}

Could you please check this issue.
Is there any fix or any workaround for it. Because so many python script are 
failing at the exit of python interpreter.

Thanks in advance

--
status: pending -> open
title: Journal execution gives fatal error in Python 3.10.1 -> GCState *gcstate 
= get_gc_state() gives fatal error in Python 3.10.2

___
Python tracker 
<https://bugs.python.org/issue46061>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue46061] GCState *gcstate = get_gc_state() gives fatal error in Python 3.10.2

2022-03-03 Thread Ajaya Sutar 


Ajaya Sutar  added the comment:

Actually we can not share code due to certain term and conditions. 

Thanks.

--

___
Python tracker 
<https://bugs.python.org/issue46061>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com