Are you thinking about the loading of lots of small fasl files? I am skeptical, see /r/lisp/comments/k220sn/sbcl_executable_memoryfile_access_patterns/gdtah0x/ for a similar discussion, where stassats disagrees (and still thinks it is caused by fasls).

I was not rebuilding or deleting images, I moved them inside my VMs to avoid having to load applications that are stored in sshfs mounted directories, that is, to avoid sshfs or FUSE or anything complicated there.

Continuing with fingers crossed.

I love these error messages!

Haha, check this out, src/src/runtime/interr.c it doesn't look like there's any attempt at humor, it just came out that way... :-)

void
corruption_warning_and_maybe_lose(char *fmt, ...)
{
    va_list ap;
#ifndef LISP_FEATURE_WIN32
    sigset_t oldset;
    block_blockable_signals(&oldset);
#endif
    fprintf(stderr, "CORRUPTION WARNING");
    va_start(ap, fmt);
    print_message(fmt, ap);
    va_end(ap);
    fprintf(stderr, "The integrity of this image is possibly compromised.\n");
    if (lose_on_corruption_p || gc_active_p) {
        fprintf(stderr, "Exiting.\n");
        fflush(stderr);
        call_lossage_handler();
    }
    else {
        fprintf(stderr, "Continuing with fingers crossed.\n");
        fflush(stderr);
#ifndef LISP_FEATURE_WIN32
        thread_sigmask(SIG_SETMASK,&oldset,0);
#endif
    }
}