OpenEuphoria

Re: 2.4 weirdness -- first report

• Posted by Robert Craig <rds at RapidEuphoria.com> Feb 23, 2003
• 426 views

Andy Serpa writes:
> I sometimes get a machine-level crash with both 2.3 & 2.4.  I'm not
> doing any peeking or poking.  I cannot reliably reproduce this crash

Please send me the program. I'll try to reproduce it on
one of my machines here.

> Now then, I have a free RAM indicator on my toolbar,
> and I can watch the amount of free memory go down as
> my programs run.  With 2.3, the memory
> goes down to a certain level and stays there.  With 2.4, during those 30
> seconds, the memory creeps back up (about 30 MB).  So I assume you've
> done something different with the garbage collection, and it is taking
> forever to release those temporary sequences for some reason?

Yes, I've changed the storage allocator significantly.
I'm using a WIN32 API routine directly.
It might be giving the memory back to the system in this situation,
rather than holding on to many megabytes of it. That takes more time though.
Perhaps you are now getting some disk paging activity too.

> return NIL

When you execute a "return" statement, it will free up all the
private variables and temps used in the subroutine.

Regards,
   Rob Craig
   Rapid Deployment Software
   http://www.RapidEuphoria.com