On Fri, 28 Sep 2012 11:40:54 -0700
Glyph wrote:
>
> Le Sep 28, 2012 à 1:10 AM, Antoine Pitrou a écrit :
>
> > (whether Python itself should try to GC-collect when MemoryError is
> > raised is an open question)
>
> Shouldn't it be doing a GC collect _before_ MemoryError is raised? (Isn't
> thi
Le Sep 28, 2012 à 1:10 AM, Antoine Pitrou a écrit :
> (whether Python itself should try to GC-collect when MemoryError is
> raised is an open question)
Shouldn't it be doing a GC collect _before_ MemoryError is raised? (Isn't this
rather the whole point of having a garbage collector?)
-glyph_
On Fri, 28 Sep 2012 00:09:23 -0700
Glyph wrote:
>
> Le Sep 27, 2012 à 7:41 PM, Benjamin Rutt a écrit :
>
> > Hi, I am trying to understand what will happen in my long-running twisted
> > server program when the available memory is low.
>
> Probably nothing good.
>
> > If I run the following
Le Sep 27, 2012 à 7:41 PM, Benjamin Rutt a écrit :
> Hi, I am trying to understand what will happen in my long-running twisted
> server program when the available memory is low.
Probably nothing good.
> If I run the following program with increasing numeric seeds as arguments, 0,
> 1, 2, 3,
Hi, I am trying to understand what will happen in my long-running twisted
server program when the available memory is low.
If I run the following program with increasing numeric seeds as arguments,
0, 1, 2, 3, 4, … , some of the time the out of memory condition will crash
and exit the program righ
