[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [pygame] More DirectX related problems



Yes, I will do that. And this first showed up only recently, once before. It was after I added repeated pygame.init()/quit() calls to surfarray_test.py. I suspect there is a connection.

Lenard

René Dudfield wrote:
hi,

I'd recommend setting up an environment variable to make windib the
default for you whilst you debug this issue.

My guess is that memory is getting overwritten somewhere causing the crash.

cu,

On Wed, Feb 4, 2009 at 11:20 AM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:
Yes, I agree it's likely buggy code. But are the problems in SDL or Pygame?
Possibly both. I am guessing that any DirectX related SDL bugs are a
write-off. The developers have no intentions of fixing them. Of course we
should continue cleaning up Pygame. The init function looks problematic.
Let's hope that helps.

Lenard


René Dudfield wrote:
hey,

sure, windows sometimes corrupts itself.  Nothing new there.
Especially if the code you are working on passes in incorrect values,
and is overwriting memory it shouldn't.

It is easy to crash many machines with a few well crafted opengl,
directx (or other video API) calls.


If using non-buggy code, that doesn't do buffer overwrites and such I
think you wouldn't have as many problems with directx.



cheers,



On Wed, Feb 4, 2009 at 10:34 AM, Lenard Lindstrom <len-l@xxxxxxxxx> wrote:

I just had personal confirmation that SDL, maybe with the help of Pygame,
does have DirectX issues. After repeated runs of surfarray_test.py and
related programs my antiquated system... reached the point that a simple
pygame.init() call would segfault.



--
Lenard Lindstrom
<len-l@xxxxxxxxx>