This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ronaldoussoren
Recipients christian.heimes, davin, docs@python, ned.deily, pitrou, ronaldoussoren, vinay0410
Date 2020-11-17.10:24:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1605608686.71.0.586692982835.issue39584@roundup.psfhosted.org>
In-reply-to
Content
Having thought about this a little more: I agree, we shouldn’t hard code a limit.  I’m not against working around misfeatures, but in this case that’s hard to do: Even if we’d limit the size of a single shared memory segment the user can create a number of them to once again use enough memory to crash the machine.

IMHO We should document that this can happen on macOS (preferable with some indication of how much shared memory can safely be used). I’ve therefore added the “Documentation” component.
History
Date User Action Args
2020-11-17 10:24:46ronaldoussorensetrecipients: + ronaldoussoren, pitrou, christian.heimes, ned.deily, docs@python, davin, vinay0410
2020-11-17 10:24:46ronaldoussorensetmessageid: <1605608686.71.0.586692982835.issue39584@roundup.psfhosted.org>
2020-11-17 10:24:46ronaldoussorenlinkissue39584 messages
2020-11-17 10:24:46ronaldoussorencreate