mmap failure misinterpreted (?) as missing file (?)

I've had multiple cases of MM (multiple versions through r3323) responding to a search by bringing up a dialog claiming a corrupted database due to database files (usually "strings" files) being missing, offering no option but to quit and implying the need for a DB rebuild, which in my (arguably pathological) case is an hours-long process from local cache and day-long task if re-fetching. Direct examination of the filesystem shows that the cited file is not actually missing but is quite big. Syslog shows an error like this:

Apr 15 06:13:39 deepfield [0x0-0x4dc4dc].com.freron.MailMate[40671]: mmap: Cannot allocate memory

I think what is actually happening is that the system has become so memory starved that it can't mmap a big file, and MM is interpreting that as the file being missing without looking more closely at the cause of the mmap failure. It is also possible that there's some sort of race condition between MM threads where the file actually doesn't exist momentarily, but is present by the time I have looked for it. With either root cause, there should be ways to avoid a forced MM restart in some cases or at least to provide a more illuminating error message for the user that does not encourage a DB rebuild that is not actually needed.

It may be related that I've recently also had a series of hard crashes clearly due to memory starvation:

Apr 15 10:24:15 deepfield [0x0-0x4dc4dc].com.freron.MailMate[0]: MailMate(55877,0xac5822c0) malloc: *** mmap(size=2097152) failed (error code=12) Apr 15 10:24:15 deepfield [0x0-0x4dc4dc].com.freron.MailMate[0]: *** error: can't allocate region Apr 15 10:24:15 deepfield [0x0-0x4dc4dc].com.freron.MailMate[0]: *** set a breakpoint in malloc_error_break to debug Apr 15 10:24:15 deepfield [0x0-0x4dc4dc].com.freron.MailMate[0]: MailMate(55877,0xac5822c0) malloc: *** mmap(size=2097152) failed (error code=12) Apr 15 10:24:15 deepfield [0x0-0x4dc4dc].com.freron.MailMate[0]: *** error: can't allocate region Apr 15 10:24:15 deepfield [0x0-0x4dc4dc].com.freron.MailMate[0]: *** set a breakpoint in malloc_error_break to debug Apr 15 10:24:15 deepfield [0x0-0x4dc4dc].com.freron.MailMate[0]: terminate called throwing an exception

Of course, sys/errno.h tells me that ENOMEM=12 and the documentation of mmap() explains some ways that can happen. With those hard crashes, the 0xac5822c0 address cited (EDI register? a fixed address???) has been the same across multiple crashes of both r3271 and r3323.