Thomas Perl

Some work on this here, but it's crashing for me at the moment on Android, not sure why: https://github.com/thp/pyotherside/commit/d931071fbd8204b1e783e4345c84b508efb79fc1 https://github.com/thp/pyotherside/commit/2378495fa960c1d3de1b1b722e57241728605e46

Thanks for your report. This can probably be done with [`Py_FinalizeEx`](https://docs.python.org/3/c-api/init.html#c.Py_FinalizeEx).

According to https://doc.qt.io/qt-5/qmake-common-projects.html, `CONFIG += dll` in `src/src.pro` could help there.

Which version of Qt 5 are you using?

Did you also install the QtQml Module development files?

Can you provide a [short, self-contained, correct example](http://sscce.org) of the bug? Or at least a stack trace/back trace (e.g. by running the affected program in `gdb`, `lldb` or some other...

I haven't had time to investigate yet. From a quick glance at the traces, it looks like the Python side keeps a reference to a Qt object that has since...

If it is really a use-after-free situation, maybe using https://doc.qt.io/qt-5/qpointer.html could be useful instead of a raw pointer to `QObject` + custom `destroyed()` handling.

You have to use a newer Python 3 for Android build, these days it should be possible to just use normal CPython sources without any patches. vitoller schrieb am Sa.,...

In general, using PyOtherSide should not result in a crash, so you've found a bug. Ideally you could compile both Qt5 and PyOtherSide with debugging support and provide a gdb...