Message-ID: <001701bec9e6$17d74ec0$4c2702c4@hultquist> From: "Carl Hultquist" To: Subject: Memory problem in DJ Date: Fri, 9 Jul 1999 10:35:12 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0014_01BEC9F6.B97D7FA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Reply-To: djgpp AT delorie DOT com This is a multi-part message in MIME format. ------=_NextPart_000_0014_01BEC9F6.B97D7FA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all. I'm trying to create a GUI program using the Allegro game library -- = this involves much creating and destroying of lists with variable length = (i.e. claiming and releasing memory throughout the program). The amount = of memory I'm using isn't much: a couple of Mb (including the graphics), = and the error only creeps in once I've looped through the main code = about 4 times (i.e. creating and destroying these lists 4 times). Then = suddenly the thing crashes with the following trace: in function __djgpp_hw_lock_end+275 followed by a trace back through my own functions. This also happens if = I constantly load bitmaps and destroy them again, but the error occurs = in the internal bitmap loading routines of Allegro so it appears that = it's not just me causing the problem! Does anyone have any ideas what's = happening and how I could fix it? Thanks. Carl -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D- tHe_xEeR e-mail: the_xeer AT iname DOT com -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-= =3D-=3D- ------=_NextPart_000_0014_01BEC9F6.B97D7FA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi all.

I'm trying to create a GUI program using the Allegro = game=20 library -- this involves much creating and destroying of lists with = variable=20 length (i.e. claiming and releasing memory throughout the program). The = amount=20 of memory I'm using isn't much: a couple of Mb (including the graphics), = and the=20 error only creeps in once I've looped through the main code about 4 = times (i.e.=20 creating and destroying these lists 4 times). Then suddenly the thing = crashes=20 with the following trace:

in function __djgpp_hw_lock_end+275

followed by a trace back through my own functions. = This also=20 happens if I constantly load bitmaps and destroy them again, but the = error=20 occurs in the internal bitmap loading routines of Allegro so it appears = that=20 it's not just me causing the problem! Does anyone have any ideas what's=20 happening and how I could fix it?

Thanks.

Carl

-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-
tHe_xEeR
e-mail: the_xeer AT iname DOT com
-=3D-=3D-=3D= -=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-
=

------=_NextPart_000_0014_01BEC9F6.B97D7FA0--