The fitsview process which displays MCS images as they finish seems to grow without bound and causes observing (and the machine) to fall behind and eventually fail.

A Gen2-driven exposure loop with the fitsview process off reads at the expected 5.5s per frame, and exposures can be streamed continuously.

With fitsview turned on the RAM usage on the machine rises until the machine basically tips over. After a fitsview restart, taking 20 frames yields a fits view process which consumes ~50% of the system RAM. Taking a second such sequence (or starting with a longer one) causes all 24 cores to rail, for all windows to become unresponsive, and for the PFS processes to no longer be able to requests visits, etc. Looks like it tops out at about ~80% RAM usage, per the widget on the screen.

Quitting fitsview clears RAM and makes the machine useable again.

We tried setting the General/Num Images preference to 2 (from 10), but that did not affect growth. You could still see one step per image in the RAM usage plot.

FWIW, we expect to read sequences of ~50 frames per telescope position this week.