delorie.com/archives/browse.cgi | search |
Message-ID: | <000a01be2303$2e21e580$b46f19c4@default> |
From: | rylan AT intekom DOT co DOT za (StefanViljoen,6599) |
To: | <djgpp AT delorie DOT com>, <shawn AT talula DOT demon DOT co DOT uk> |
X-Mailer: | Microsoft Outlook Express 4.72.2106.4 |
Subject: | Allegro do_dialog causing memory leak? |
Date: | Wed, 9 Dec 1998 01:32:10 +0200 |
X-MimeOLE: | Produced By Microsoft MimeOLE V4.72.2106.4 |
Reply-To: | djgpp AT delorie DOT com |
Hi, I have run into a quandry while using allegro's dialog procedures. I have noticed that a function that I had that called do_dialog seems to be leaking memory (exatly 8k 8192 bytes.) Since this function also creates and clears a linked list, I first suspected that I was leaving a node allocated, but this proved not to be the case - I traced the memory leak to the do_dialog.... Anybody else encounter this? Recursive calls to do_dialog (the dialog tested only contains the d_keyboard_proc dialog function) starts eating up memory until the system is constantly paging to disk. I detected the leak by using go_32_remaining_physical_memory before and after the call to the dialog procedure. It reports the 8k discrepancy. Anybody ever encounter this problem with do_dialog? Am I doing something wrong? How can it be fixed? Fanx! -- Spawned By Rylan Is truth beauty or beauty truth? http://home.intekom.com/rylan/index.html
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |