OK... the way I'm understanding is this:
xfbb checks /proc/meminfo (by what process it does this, I'm not clear on),
and if it gets an indication of low memory... or actually anything other
than an indication of sufficient memory, then it hangs, waiting for a
process to free some memory.
Since /proc/meminfo is different now, xfbb never gets an indication of
sufficient memory... so it just waits forever.
Question: is xfbb checking /proc/meminfo directly, or is it using another
program to check it?
Next question: how do we avoid this problem? A 2.1.41+ version of xfbb?