STINNER Victor <vstin...@redhat.com> added the comment:
> Say a library calls CreateEventW and gets handle 32. It passes this handle to > some other library, which uses the event and closes the handle when it no > longer needs it. But due to a miscommunication in the documentation, the > first library thinks the handle remains open. Now handle 32 is free for > reuse, but the library doesn't know this. subprocess.Popen subsequently calls > CreateProcessW and gets handle 32. Later on, the library closes handle 32, > making it invalid, at least until it gets assigned to some other kernel > object. So yeah, it's a severe bug in an application. An application should not close the wrong handle by mistake :-) Thanks for the explanation. So it would be "nice" to backport the change to reduce the impact of such application bug, but it's not really a bug in Python itself. Python cannot fully protect developers for such class of bugs. On Unix, there is a similar bug with applications trying to close a file descriptor which is already closed. It can lead to very severe bugs (crashes): https://bugs.python.org/issue18748 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue37380> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
