Re: Gradual Growth of Memory Use?

Yes, HCL:GC-GENERATION affects all running threads.

Is the gradual growth up to 1.5 GB reported in the output of (room) or the
return values of (system:room-values)?  In particular the "total allocated"
and "total size" values.

If so, then the output of (room t) periodically might be useful to see.

If not, then the problem is outside Lisp.

What is the plotting library using for the graphics?

-- 
Martin Simmons
LispWorks Ltd
http://www.lispworks.com/



>>>>> On Wed, 12 Mar 2025 05:34:15 -0700, David McClain (as dbm at refined-audiometrics dot com) said:
> 
> The system produces live data plots, and there are some graphics elements that need to be allocated and freed for each graph redraw. I have tried eliding those allocations during plotting to see of that was the cause of memory leaks, and it appears not to be the case.
> 
> 
> 
> > On Mar 12, 2025, at 05:27, David McClain <[email protected]> wrote:
> > 
> > PS: The computer is an AMD Rizen 5 with 32 GB RAM. So no shortage of physical memory, and no reason to be paging anything. The CPU load is around 5-7% during data acquisition and recording to external disk memory. Nothing else is overtly running in the computer, but Windows/11 may have other ideas about that…
> > 
> > 
> > 
> >> On Mar 12, 2025, at 05:17, David McClain <[email protected]> wrote:
> >> 
> >> My daily data acquisition system now runs about 24 hours between failures. The symptoms are ever increasing memory use, starting at 130 MB and growing to 1.5 GB, and then DAC-read failures where samples are erratically and consistently dropped, causing growing distortions of the measured items.
> >> 
> >> I’m doing (HCL:GC-GENERATION T) every time through the outer loop, about once per 15 sec. Memory buffers for DAC reading were initially established in Windows/11 and locked down by the system, yet during these later acquisitions the system acts like the locked buffers have been paged out, causing excess delay in arriving for use by the underlying MMIO system of Windows/11.
> >> 
> >> My normal mode of operation has been to acquire data each day in two groups. First is several hours surrounding Sunrise, and second, several hours surrounding Sunset. Those contain the most interesting events. The system normally goes haywire around 4 am, at which time I simply shut it down, exit the Lisp system, and then restart from cold. 
> >> 
> >> My assumption is that HCL:GC-GENERATION affects all running threads in the system, and not just the one thread performing the GC. Maybe that is mistaken?
> >> 
> >> - DM
> > 
> 
> 
> _______________________________________________
> Lisp Hug - the mailing list for LispWorks users
> [email protected]
> http://www.lispworks.com/support/lisp-hug.html
> 

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
[email protected]
http://www.lispworks.com/support/lisp-hug.html