Anyone Here Familiar With ESPAsyncWebServer/LittleFS Internals?

I've been tearing my hair out for the last week or more, trying to track down the source of just plain flaky operation of the ESPAsyncWebserver. It appears to be randomly crashing, leaving no real clues as to why. I'm not getting any exceptions but the ESP is crashing an re-starting. I've turned on the debugging output from the WebServer and filesystem, and it appears to be crashing in the middle of file accesses, but I don't know what the debug messages mean. Here is what I see:

wifi evt: 7
wifi evt: 7
wifi evt: 7
gaugecal.html start
gaugecal.html done
lfs_file_close: fd=0x3fff7d1c
gaugecal.css start
gaugecal.css done
gaugecal.js start
gaugecal.js done
lfs_file_close: fd=0x3fff784c
lfs_file_close: fd=0x3fff8cbc
lfs_file_close: fd=0x3fffa01c
bright.png start
bright.png done
lfs_file_close: fd=0x3fffad0c
lfs_file_close: fd=0x3fff84cc
lfs_file_close: fd=0x3fff6ec4
wifi evt: 7
gaugecal.html start
gaugecal.html done
lfs_file_close: fd=0x3fff8284
gaugecal.css start
gaugecal.css done
gaugecal.js start
gaugecal.js done
lfs_file_close: fd=0x3fff79b4
lfs_file_close: fd=0x3fff9c24
lfs_file_close: fd=0x3fff8c34
lfs_file_close: fd=0x3fffac04
bright.png start
bright.png done
lfs_file_close: fd=0x3fffa054
lfs_file_close: fd=0x3fff6ec4
wifi evt: 7
gaugecal.html start
gaugecal.html done
gaugecal.css start
gaugecal.css done
gaugecal.js start
:oom(24)@abi.cpp:38
:oom(21)@File: 0x402671d0:111
:oom(21)@File: 0x402671d0:111
:oom(21)@File: 0x402671d0:111
:oom(21)@File: 0x402671d0:111
:oom(21)@File: 0x402671d0:111
:oom(@▒ *▒ԕ▒▒*▒D▒І      ▒▒"▒FI▒▒▒▒P▒▒▒▒RL*66▒    <<==== HERE IS WHERE IT CRASHES
▒
SDK:2.2.2-dev(38a443e)/Core:2.7.3-3-g2843a5ac=20703003/lwIP:STABLE-2_1_2_RELEASE/glue:1.2-30-g92add50/BearSSL:5c771be


setup()



Starting Master Controller




FSInfo:
   totalBytes: 2072576
    usedBytes: 1146880
    blockSize: 8192
     pageSize: 256
 maxOpenFiles: 5
maxPathLength: 32

I have eliminated pretty much ALL of my code, other than the server setup code (a bunch of server.on() statements). My loop() is empty. The HTML/CSS/js all works flawlessly on my PC.

Does anyone know where the above messages (:oom(21)....) are coming from, and what they mean?

Could this be a memory issue? I have roughly 50% free RAM, but the webpages that load several files, or larger files, are MUCH more likely to have trouble than the ones that only load a few files. Could the randomness be a result of the server consuming too much RAM attempting to send too many files at one time? Is there a way to force a chunked response, so it uses less RAM?