Memory leak! - Axe Software Forums

  Axe Software Forums
  Quest Developer Forum
  Memory leak!

Author Topic:   Memory leak!

Mega posted 17-10-2001 05:53 GMT
When I'm programming, typically I write some new code, run it, try to fix whatever went wrong, run it again, and so on. After a bunch of runs, however, even if I only changed a tiny bit of code, I start getting "Runtime error: out of memory" messages, and I have to close some other applications in order to keep working. This leads me to believe that Quest is somehow leaking memory. Is there some manual procedure to free up the memory it uses for variables and stuff? Or does Quest do all that automatically? -- in which case, it's not doing it right.
Alex posted 17-10-2001 18:27 GMT
There are not many times that I need to think about destroying variables etc. as VB does most of that automatically. I'll have a more detailed look at some point. It could be a problem with VB itself, or more likely it could be down to the operating system - are you using Windows 9x?
Mega posted 18-10-2001 01:46 GMT
I'm using Windows ME.
Alex posted 18-10-2001 18:26 GMT
Yes, Windows ME is not as good at organising memory as Windows NT/2000/XP, but I'll take a look and see if there's anything I can fix anyway.

Author	Topic: Memory leak!
Mega	posted 17-10-2001 05:53 GMT When I'm programming, typically I write some new code, run it, try to fix whatever went wrong, run it again, and so on. After a bunch of runs, however, even if I only changed a tiny bit of code, I start getting "Runtime error: out of memory" messages, and I have to close some other applications in order to keep working. This leads me to believe that Quest is somehow leaking memory. Is there some manual procedure to free up the memory it uses for variables and stuff? Or does Quest do all that automatically? -- in which case, it's not doing it right.
Alex	posted 17-10-2001 18:27 GMT There are not many times that I need to think about destroying variables etc. as VB does most of that automatically. I'll have a more detailed look at some point. It could be a problem with VB itself, or more likely it could be down to the operating system - are you using Windows 9x?
Mega	posted 18-10-2001 01:46 GMT I'm using Windows ME.
Alex	posted 18-10-2001 18:26 GMT Yes, Windows ME is not as good at organising memory as Windows NT/2000/XP, but I'll take a look and see if there's anything I can fix anyway.