Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!news2.arglkargh.de!news.wiretrip.org!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.012 X-Spam-Evidence: '*H*': 0.98; '*S*': 0.00; 'python?': 0.05; 'ram': 0.05; 'python': 0.08; '32-bit': 0.09; 'hits': 0.09; 'am,': 0.12; '8:40': 0.16; 'dumps': 0.16; 'have,': 0.16; 'wrote:': 0.16; 'wed,': 0.17; 'linux': 0.17; 'cheers,': 0.18; 'subject:list': 0.18; 'stick': 0.18; 'seems': 0.20; 'memory': 0.21; 'badly': 0.21; 'header:In-Reply-To:1': 0.22; 'versions': 0.23; '64-bit': 0.23; 'starts': 0.24; 'aug': 0.24; 'windows': 0.26; 'problem': 0.28; 'url:mailman': 0.28; 'message-id:@mail.gmail.com': 0.29; 'chris': 0.32; 'does': 0.32; "isn't": 0.33; 'sort': 0.33; 'too': 0.33; 'to:addr:python-list': 0.33; 'url:listinfo': 0.33; 'things': 0.34; 'url:python': 0.36; 'fair': 0.37; 'using': 0.37; 'steven': 0.38; 'some': 0.38; 'received:google.com': 0.38; 'url:org': 0.38; 'received:209.85': 0.38; 'subject:: ': 0.39; 'subject:with': 0.39; "there's": 0.39; 'to:addr:python.org': 0.39; 'processing': 0.40; 'more': 0.60; 'your': 0.61; 'url:co': 0.63; '31,': 0.64; 'batch': 0.64; 'here': 0.65; 'limit': 0.66; 'crash': 0.67; 'physically': 0.84; 'incidents': 0.93 MIME-Version: 1.0 In-Reply-To: <4E5E2BCB.5090903@simplistix.co.uk> References: <4e5e2a0c$0$29965$c3e8da3$5496439d@news.astraweb.com> <4E5E2BCB.5090903@simplistix.co.uk> Date: Wed, 31 Aug 2011 08:49:24 -0400 Subject: Re: PC locks up with list operations From: Benjamin Kaplan To: python-list@python.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Junkmail-Status: score=10/49, host=mpv2.tis.cwru.edu X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A020209.4E5E2DD6.004B,ss=1,fgs=0, ip=209.85.215.170, so=2010-12-23 16:51:53, dmn=2009-09-10 00:05:08, mode=single engine X-Junkmail-IWF: false X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 33 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1314795040 news.xs4all.nl 2480 [2001:888:2000:d::a6]:52606 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:12472 On Wed, Aug 31, 2011 at 8:40 AM, Chris Withers wro= te: > > On 31/08/2011 13:33, Steven D'Aprano wrote: >> >> I am using Linux desktops; both incidents were with Python 2.5. Do newer >> versions of Python respond to this sort of situation more gracefully? > > Ironically, Windows does better here and dumps you out with a MemoryError= before slowly recovering. > > Linux seems to fair badly when programs use more memory than physically a= vailable. Perhaps there's some per-process thing that can be used to limit = things on Linux? > > cheers, > > Chris > > -- 32-bit or 64-bit Python? A 32-bit program will crash once memory hits 2GB. A 64-bit program will just keep consuming RAM until your computer starts thrashing. The problem isn't your program using more RAM than you have, just more RAM than you have free. Last time I faced a situation like this, I just decided it was better to stick to the 32-bit program and let it crash if it got too big. > Simplistix - Content Management, Batch Processing & Python Consulting > =A0 =A0 =A0 =A0 =A0 =A0- http://www.simplistix.co.uk > -- > http://mail.python.org/mailman/listinfo/python-list