[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[pygame] surfaces and memory
- To: pygame-users@xxxxxxxx
- Subject: [pygame] surfaces and memory
- From: Luke Miller <dodgyville@xxxxxxxxx>
- Date: Sat, 20 Aug 2005 12:19:44 +1000
- Delivered-to: archiver@seul.org
- Delivered-to: pygame-users-outgoing@seul.org
- Delivered-to: pygame-users@seul.org
- Delivery-date: Fri, 19 Aug 2005 22:20:09 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=sCkQAWConJUil6iNkkvsnaEwQKDTogjRls8vJfgWyRceY8J8EwHMD95GEOWurnVeEciTjzqrS1MDZELzj2CYWlnyzsZ3pN3/NKrfrgFFdDmbfJnG5j5DbVc6hqe4g6bBEnCEcu0+dqzYsEypYz1tzn/gAd1EIn1pa1i7GNwGoS8=
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
Hi everyone.
I have a very complicated animation (100+ frames) I want to load up in
pygame. When I load each image individually, it loads (takes a while to
read from disk though) and then runs fine. However, when I compile the
frames into a wide montage in a single file and try to load it as one
surface, I get:
<pygame.error instance at 0x4029896c> Out of memory exceptions.
Two questions:
Does anyone have an idea of how big a surface can be?
And also, does anyone know the best way to debug pygame?
Thanks,
Luke