Filipp Andjelo added the comment: Hm, this is strange, because close() can only be called from the same thread and dealloc() can be called only if reference count is 0, right? So why is there a mutex again each other anyway? And how can that be, that sqlite3_close() is called multiple times with the same pointer? We are getting a crash, which is only possible if dealloc() is called where close() is not yet done. Is this possible? Or do I understand something wrong? For such cases we also have to set database pointer to NULL in dealloc(), but it looks like the problem is somewhere different, the whole code looks strange for me.
---------- Added file: http://bugs.python.org/file41970/sqlite_connection.c.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26387> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
