search

abscorpy / stardog

Automatically exported from code.google.com/p/stardog
0 stars 0 forks source link

Memory Leak: pygame out of memory crash #33

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Pygame can run out of memory from creating too many surfaces.  This is a fatal 
error.  I encountered this once landing on a planet with tons of parts on it 
(ships currently will just keep crashing into the planet so you can farm them), 
and looking at the parts menu.

First step is to change all pygame.transform calls to re-use an output Surface. 

Second step is to audit everything else that creates a Surface.  Also look into 
whether there's anyway to completely immediately destroy a Surface in pygame.

Original issue reported on code.google.com by TheMissingLint@gmail.com on 20 May 2013 at 5:55

GoogleCodeExporter commented 8 years ago 
alright, false alarm: python cleans up old surfaces properly.  This means there 
is a memory leak somewhere.

Original comment by TheMissingLint@gmail.com on 21 May 2013 at 4:46

GoogleCodeExporter commented 8 years ago 
the worst of this error was in Class BG draw method wrong implementation of 
PixelArray.
Discovered by Robert.

Original comment by aapska...@gmail.com on 8 Dec 2014 at 9:08

GoogleCodeExporter commented 8 years ago 
Aaand we have one in colorShift in the utils file the PixelArray pa on 130 ?
All is fixed if all is well.

Original comment by aapska...@gmail.com on 8 Dec 2014 at 9:12