flist -- "Killed" -- oom (*not* 1.8 related)

[Greg Minshall]

hi.

for some years now, i occasionally get in a situation where flist
gobbles up lots of memory, and is then killed by the kernel's "oom"
procedure.  eventually this goes away, though i'm not exactly sure how
that happens either.

----
bash archlinux (master): {50071} flist -sequence unseen -all -recurse
Killed
bash archlinux (master): {50072} flist -sequence unseen -all
Killed
bash archlinux (master): {50073} flist -sequence unseen
drafts+ has 0 in sequence unseen; out of 1
bash archlinux (master): {50074} flist -sequence xyz -all
Killed
bash archlinux (master): {50075} flist -version
flist -- nmh-1.7.1 built 2022-11-25 04:27:57 +0000 on archlinux
----

any ideas?

and, if not, any thoughts on how to debug?  if i build "cc -g", any
thoughts on where to set breakpoints, or where to insert printf's, to
try to track this down?

cheers, Greg