Matthias Reichl added the comment:
We were hitting the same issue in kodi, which uses embedded sub-interpreters to
run python addons, after one of the addons was switched to asyncio.
The immediate cause of the assertion failure is a use-after-free issue from the
running loop holder cache:
When the running loop holder is deallocated (which happens eg on interpreter
shutdown) cached_running_holder holds a dangling pointer.
A subsequent call to get_running_loop() may then pick that up and boom.
While probably not a full fix for this issue I think it would be good to fix
the use-after-free problem - there could be other code paths that lead to this
situation. I've created a github pull request for that
--
___
Python tracker
<https://bugs.python.org/issue45262>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
