Re: Gradual Growth of Memory Use?

"Yuri Davidovsky (as work at disclosure dot ie)" <[email protected]>
Newsgroups gmane.lisp.lispworks.general
Message-ID <[email protected]>
> On 15 Mar 2025, at 13:24, David McClain <[email protected]> wrote:
> 
> Memory use at start was 130 MB, growing to over 2 GB at finish.
> 
> I still cannot account for massive memory growth, but I suspect that it has to do with the running graphic display of a synthesized image (waterfall display).

That is puzzling. The amount of data you are collecting is actually minuscule so it should not inflate the heap so much. GUI code indeed can be a memory hog so your suspicion is warranted. Not too sure what it could be though, pixmap ports being instantiated for each graphics port redraw but not being discarded afterwards? Are there any CAPI resources instantiated that need to be manually destroyed after, or at least let go?

> 
> The overall memory use grows from 4 GB to over 9 GB, with no compressed memory showing. But the “hog” in the memory is Explorer.exe (!), at over 7 GB. I am not overtly running any instances of Explorer.

That is just windows' graphical shell, not sure why they called it like that, it does get people confused regularly due to the fact that the file explorer is called explorer, and there was also internet explorer not that long ago.

> 
> When I reboot the system and begin anew, the monitor shows that Explorer.exe is launched just after I launch LWW. LWW PID = 7028, Explorer PID = 7048. At start, we have LWW memory at 130 MB, and Explorer at 110 MB. I did not invoke explorer.exe, but maybe the CAPI graphics system does this?

I would not worry about explorer.exe typically, but since your suspicion is that the memory consumption is GUI or CAPI related and  explorer manages desktop display, it may be a sign of something going on. Your app generating some visual data that gets copied over somewhere where explorer has access too so they grow together?

Have you tried disabling the automatic plotting function of the app and only refresh it manually when you need it? That would help to narrow down whether the memory usage increase is related to the gui of the app.



_______________________________________________
Lisp Hug - the mailing list for LispWorks users
[email protected]
http://www.lispworks.com/support/lisp-hug.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.