My C# Console script doesn't finish when using(Py.GIL()) finish it's execution #1687

Same problem

@Maskliv Found solution. You have to call PythonEngine.Shutdown(); after you finished working with Python.

If I call PythonEngine.Shutdown() after using (Py.GIL()) {..} I get an "Segmentation fault" error?
Debian 11, Bullseye
Python 3.9.2

UPDATE:
It only happens when using numpy. But I remember now it says somewhere there is issues with this particular module and it relate to a bug in the module. Don't see the issue in another module (apt, the Debian package management tool).
For me it look like everything is not released/disposed when Py.GIL() is disposed, either using a "using" block or calling Py.GIL.Dispose() manually.
But it's not because numpy is "hanging" outside pythonnet. If I restart pytonnet (restart my C# app") numpy is not hanging anymore, so it's surprising pythonnet cannot release it fully.

Calling shutdown using stripped down numpy sample I get:

Fatal Python error: auto-releasing thread-state, but no thread-state for this thread

using System;
using Python.Runtime;

namespace test
{
    class Program
    {
        static void Main(string[] args)
        {
            Console.WriteLine("Hello, World!");
            using (Python.Runtime.Py.GIL())
            {
                dynamic np = Python.Runtime.Py.Import("numpy");
                Console.WriteLine(np.cos(np.pi * 2));
                PythonEngine.Shutdown();
            }
        }
    }
}

I would expect to place PythonEngine.Shutdown(); after the using statement.

@MrM40 doing as you suggest, works also for me properly without any issue!

I would tend to close such issues actually.