[issue16929] poll()/epoll() are not thread-safe

Changes by Charles-François Natali : -- status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue16929] poll()/epoll() are not thread-safe

Charles-François Natali added the comment: OK, I'll close as duplicate. -- dependencies: -select.poll is not thread safe resolution: -> duplicate superseder: -> select.poll is not thread safe ___ Python tracker

[issue16929] poll()/epoll() are not thread-safe

Changes by Serhiy Storchaka : -- dependencies: +select.poll is not thread safe ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue16929] poll()/epoll() are not thread-safe

Serhiy Storchaka added the comment: For poll() see issue8865. -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list m

[issue16929] poll()/epoll() are not thread-safe

New submission from Charles-François Natali: After optimizing epoll() to use a per-instance buffer like poll() does (http://bugs.python.org/issue16876), I realized that it wasn't thread-safe, and can result in crashes: """ ./python /tmp/test.py *** glibc detected *** ./python: free(): corrupte