- Python Home
- About
- News
- Documentation
- Downloads
- Community
- Foundation
- Developer's Guide
- Issue Tracker
- Issues
- Summaries
- User
- Administration
- Help
Message217307
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 | neologix |
|---|---|
| Recipients | josh.r, jtaylor, neologix, njs, pitrou, skrah, vstinner |
| Date | 2014-04-27.19:03:45 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <CAH_1eM1CyDRTvhbF2OsqeP2xy2VSNhGLXmyzMRozrAH-ZYQQHw@mail.gmail.com> |
| In-reply-to | <1398623846.2380.4.camel@fsol> |
| Content | |
|---|---|
> Both OOM here (3.11.0-20-generic, 64-bit, Ubuntu). Hm... What's /proc/sys/vm/overcommit_memory ? If it's set to 0, then the kernel will always overcommit. If you set it to 2, normally you'd definitely get ENOMEM (which is IMO much nicer than getting nuked by the OOM killer, especially because, like in real life, there's often collateral damage ;-) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-04-27 19:03:45 | neologix | set | recipients: + neologix, pitrou, vstinner, njs, skrah, jtaylor, josh.r |
| 2014-04-27 19:03:45 | neologix | link | issue21233 messages |
| 2014-04-27 19:03:45 | neologix | create | |

