Not good news I’m afraid. I ran your test program on Windows XP (DX8) and it
ran fine:- (This is after about 5 minutes)
Cycle: 9832 seconds: 0.020000
Cycle: 9833 seconds: 0.020000
Cycle: 9834 seconds: 0.020000
Cycle: 9835 seconds: 0.020000
Cycle: 9836 seconds: 0.020000
Cycle: 9837 seconds: 0.020000
Cycle: 9838 seconds: 0.010000
I guess that means that there is either a problem with SDL when it is using
WINDIB, or there is a problem with your videodriver.
Furthermore, the memory usage remained absolutely constant for the entire
duration of the test. It is therefore unclear why you were seeing excessing
memory usage and swapping.
I don’t have access to a machine running Windows NT4 until 2nd January, but
would be happy to try it again then.
Steve> ----- Original Message -----
From: Gib Bogle
To: sdl at libsdl.org
Sent: 26/12/01 17:51
Subject: [SDL] Re: Windows NT4 issues (Steve Lupton)
SDL on Win32 uses DirectX 5 or later for its hardware acceleration.
NT 4 only supports DirectX 3.
I am not speaking completely authoritatively on this matter but I do
that this is where your problem lies. Perhaps someone else can confirm
Either you are creating a memory leak, or SDL is - why don’t you post
fragment showing what you are doing?
Someone else on the list will be able to confirm the behaviour you are
seeing, or point out where the problem is.
Steve, the hypothesis that DirectX incompatibility is the cause of my
problems is a good one. Following your suggestion, here is my test
program. You’ll see that only SDL_SetPalette() gets called repeatedly.
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.