[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [pygame] Clock.tick() freeze.
- To: pygame-users@xxxxxxxx
- Subject: Re: [pygame] Clock.tick() freeze.
- From: "René Dudfield" <renesd@xxxxxxxxx>
- Date: Wed, 3 Dec 2008 13:06:25 +1100
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: pygame-users-outgoing@xxxxxxxx
- Delivered-to: pygame-users@xxxxxxxx
- Delivery-date: Tue, 02 Dec 2008 21:06:45 -0500
- 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=Y9mXnBHvXFeR5FfAvn5xEto8stpSXvDDZqp5+jc677g=; b=PNo4BK69r/st2M0EQ7bqV/vdUBywkeGWGYYfNgxXT8LSsyXro2WniWpF7l05CbJLFo LsdOOwuYovh2LENIJAu2KyGnAxdwx9UNPF4zPAL5pPgQdN3fq4lFyfHLRTl0/J8hdWWL rJvsfkXsMCQIDHscXlyiD0L3559rVkFkgsa80=
- 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=lGrKGipqOnwMWtPYwbtZQv1TtWwzCmBkhhYsm6h48RMY1f/rZRpqta2prnCE93JxX/ ExpMniLF0bR9a2IAqo6S0sFWpc7+G8h6uykMr3SrHBjfqjmbUAQItBXXP44Ky4o+gW5u 9RcGavYqt//LPZGBFmjtP3+9kaOH8SSUChTY8=
- In-reply-to: <20081202104004.GA3749@home>
- References: <20081202104004.GA3749@home>
- Reply-to: pygame-users@xxxxxxxx
- Sender: owner-pygame-users@xxxxxxxx
hi,
I'd suggest trying out a newer pygame... there were a few 64bit fixes
made since 1.7.1
cu,
On Tue, Dec 2, 2008 at 9:40 PM, Peter Gebauer
<peter.gebauer@xxxxxxxxxxxxxxxxxxxxx> wrote:
> Hi!
>
> I've tried googling, but came up with nothing. I'm using the Debian testing
> (AMD64) version of pygame (1.7.1release-4.2), sometimes when Clock.tick() is
> called the entire Python process will hang, only SIGKILL will actually stop
> it. Anybody recognize this bug? Is it fixed in later versions?
>
> /Peter
>
>