STINNER Victor added the comment: 2015-03-16 17:41 GMT+01:00 Antoine Pitrou <rep...@bugs.python.org>: > Note that PIPE_MAX_SIZE can be large. Perhaps move the memory allocation > (i.e. `item * (support.PIPE_MAX_SIZE // len(item) + 1)`) before the alarm(1) > call?
Good idea, the first strace shows that SIGALRM was received while Python was creating the large data. I made this simple change. Can you tell me if my change fixes the issue? > Or what if alarm_interrupt is simply set up to retrigger the signal? It may make the test more reliable and I don't see how it can fix the issue showed in the strace. Feel free to make the test more reliable with such change if you want. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue23680> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
