[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Another blitting surface to itself crash
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Another blitting surface to itself crash
- From: "Hugo Arts" <hugo.yoshi@xxxxxxxxx>
- Date: Sat, 2 Aug 2008 23:32:18 +0100
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: pygame-users-outgoing@xxxxxxxx
- Delivered-to: pygame-users@xxxxxxxx
- Delivery-date: Sat, 02 Aug 2008 18:32:26 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=rnsAEuhAZBA59A4YbS0o6EI/mj+s/8QkphnLvFHLdRo=; b=GHtgo+JkDXgvtrY4wuRAtgHKloK9q/zovvXncQMDNqCSW8EfucqXJPbxAhEjsv2aK7 a0WTD7neBSDgMzjReKvIWuaAmttK3WksIPMxhUpqf37SwxnfmrRtFbmMNsD5+cuyQj9p f03uVRrAFwPuJYsxwucQZ6zrNRaMqdpw3qC5I=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=BQY7B5pHWOZ9zgl3rjjttfqEEC/NSBQTAfWOFxHc4gDkuHcojMwbmO+vP9oYudCPhn es7piM/7+l5NUn2HmyHsI+10AizrY6ing0b9L6eu+PcS2ec3h2vuI0TB6Azwn0g92mX8 JdCyu/Wnd8PWWrFtw1px3VVnivN1DUUhP9Xnc=
- In-reply-to: <e55f7e400808021030j5e3fdf7ftf0734359cfacbf9@xxxxxxxxxxxxxx>
- References: <e55f7e400808021030j5e3fdf7ftf0734359cfacbf9@xxxxxxxxxxxxxx>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
On Sat, Aug 2, 2008 at 6:30 PM, Brian Fisher <brian@xxxxxxxxxxxxxxxxxxx> wrote:
> There's another instance of blitting a surface to itself crashing on Windows
> for a user, it's believed to be a 1.8.1 thing by the poster
> http://pygame.motherhamster.org/bugzilla/show_bug.cgi?id=19
>
> last time it came up marcus was thinking about making pygame throw an
> exception on blitting a surface to itself, which still seems like a decent
> solution to me. Anybody know any more background?
>
I was the one who submitted the bug last time. At the time there was
some resistance to the exception solution, since scrolling was seen as
a valid reason to blit surfaces onto themselves, as well as a certain
meltdown effect.
There is an easy workaround available (just copy the surface), but no
fix. As far as I could tell, the bug occurs only on windows.
We never got into the cause of the bug, the thread died down without
any real bug hunting done. I have no idea what could be causing this.
At the time I wrote this minimal script to reproduce, works also in
interactive mode:
import pygame
pygame.init()
a = pygame.Surface((10, 10))
a.blit(a, (0, 0))
Output:
Fatal Python error: (pygame parachute) Segmentation Fault
That's about all I know.
Hugo