On mer, 2014-07-16 at 15:10 -0700, B W wrote:
> Argh! pygame.mixer.quit() is hanging.
If you're comfortable with compiling pygame, then I'd keep drilling
down, sprinkling more prints into mixer.c/autoquit() to see which line
of that function it fails on. The last line appears to tell SDL to
shutdo
pygame is doing something unorthodox with the
threading that throws it off.
I haven't tried the solutions proposed for previous problems with pygame and
pulseaudio yet.
Hasvers
- Mail original -
De: "B W"
À: "N:"
Envoyé: Mercredi 16 Juillet 2014 18:10:41
Objet
Argh! pygame.mixer.quit() is hanging.
('keydown', 'escape')
Exit progress: begin
Exit progress: pygame.display.get_init()
Exit progress: pygame.display.get_surface()
Exit progress: screen.unlock()
Exit progress: pygame.display.set_mode((16, 64))
Exit progress: pygame.display.flip()
Exit progress:
On mer, 2014-07-16 at 14:36 -0700, B W wrote:
> The issue seems to be in the shutdown/cleanup code of pygame.
The program appears to only use the pygame.display module, so if it is
currently crashing in pygame.exit(), then it may be an idea to try
initialising and exiting individual modules, to se
Hey, I bet you forgot about me! :)
I finally upgraded to Ubuntu 14.04. Alas, this problem did not go away.
Since the last message:
- I learned it doesn't matter if FPS is artificially capped; but faster FPS
seems to make the problem occur more reliably. This rules out throttled vs.
un-throttled.
Hi, DR0ID,
While it may not be elegant there is nothing syntactically wrong with
what I did in the event loop. :) When the misbehavior is not occurring
there is no problem exiting the program as it is designed.
To get to the bottom of this I think someone with the right skills and
knowledge
Hi, Jake,
This is not true. A process's default action for an unhandled event is
to abort. During normal execution, when the problem is not occurring, an
unhandled SIGTERM aborts the process just fine.
Gumm
On 6/29/2014 00:48, Jake b wrote:
> SIGTERM (15) does not kill the program. SIGKILL
On 2014-06-28 19:14, bw wrote:
if e.key == K_ESCAPE:
print(1)
pygame.display.get_init()
print(2)
pygame.display.get_surface()
print(3)
screen.unlock()
print(4)
pygame.di
> SIGTERM (15) does not kill the program. SIGKILL (9) does.
You need to handle event QUIT.
if e.key == K_ESCAPE:
print(1)
pygame.display.get_init()
print(2)
pygame.display.get_surface()
print(3)
screen.unlock()
print(4)
pygame.display.set_mode((16,
On ven, 2014-06-27 at 22:35 -0700, bw wrote:
> I attached the small program. I'm curious if anyone can run it and
> reproduce the problem. I plan on upgrading Ubuntu soon, when I am ready
> to risk it: maybe the problem will go away. I'll post the outcome--but
> I've been too busy to risk the up
Howdy,
Hoping some folks can try this out. I have no idea why it is happening.
Not even a theory. Could be anything from drivers to the Python or SDL
build. Here's the scoop...
The environment:
- i5 desktop computer (not a virtual machine)
- Ubuntu 13.04 x86_64
- Python 2.7
- pygame 1.9.1
Th
12 matches
Mail list logo
