did you try running python with -B flag?

did you try running python with -B flag?

I've tried this: in 4 of 5 attempts, python interpreter 3.5 64-bit crashes at the exit. No pycache directores exist in this case.

I haven't seen yoyr sample code, this isn't related to the sub classing bug right? I'm curious if pycache existed when the subclass tests failed

You zip file does not include Axa.* .NET dependencies.

@vmuriart
I do subclass in sample and I believe it is related. In real assembly I have subclassing and strange effects. If I remove subclassing then it works.

@denfromufa
I do not understand. Well, I am not .NET pro. I compile with run.bat in Visual Studio 2015 Upd3 Developer Prompt and see only:
C:\dev\job3>csc /target:library /debug:full class.cs
Microsoft (R) Visual C# Compiler version 1.3.1.60616
Copyright (C) Microsoft Corporation. All rights reserved.

and class.dll is made somehow.

@vmuriart
I tested and removing subclassing in sample code or just removing __namespace__ in adapter.py fixes the issue. Do you have an idea what this bug is ? Or may be it is fixed already??

I see that it is self-contained now - Aka namespace is in the same class.cs.

I nailed bug in src\runtime\typemananger.cs in CreateSubType(): method Runtime.XIncref() is not called, but PyObject is created and added to disposeList. Correct code:

if (0 != Runtime.PyMapping_HasKey(py_dict, assemblyKey.Handle))
{
	var pyAssembly = new PyObject(Runtime.PyDict_GetItem(py_dict, assemblyKey.Handle));
	Runtime.XIncref(pyAssembly.Handle);
	...
}
...
if (0 != Runtime.PyMapping_HasKey(py_dict, namespaceKey.Handle))
{
	var pyNamespace = new PyObject(Runtime.PyDict_GetItem(py_dict, namespaceKey.Handle));
	Runtime.XIncref(pyNamespace.Handle);
...
}

Now it doesn't crash anymore.

Would be not easy to make regression test out of it. I realized that no crash if this code is completely in one .py. It must be spread among several modules to provoke garbage collector crash.

Nice! The subclass tests might catch this. Even though it's intermittent I run it multiple times each version to check for it.

If it works in your tests then you can submit this patch to repo.

@testrunner123 would you like to submit a pull request? otherwise someone can do this for you and attribute the commit to you git commit --author="???"

Hmm, we had quite a few of those. Maybe we should replace the current new PyObject by more explicit constructors like PyObject.FromPtrIncref, PyObject.BorrowFromPtr? I don't really have good names, though.

@filmor i agree about PyObject.FromPtrIncref, when would PyObject.BorrowFromPtr happen?

I didn't think much about the names, I'll try to get a PR up with a proposal for explicit constructors.

@filmor the fix seems to be merged. Can this bug be closed?

I think so, yes.