Ship unrecoverably crashed after hitting loom limit via HTTP file upload & eyre cache insertion

[tinnus-napbus]

I have a files app that takes a file via an HTTP POST request, saves it in state and inserts it in the Eyre cache for quick access via the browser. I repeatedly uploaded large files until it presumably hit the loom limit and crashed with bail:meme. Upon attempting ship restart it just crashed again, and will no longer start. Crashing is perhaps understandable but it presumably shouldn't permanently brick the ship.

initial crash:

bail: meme
home: bailing out
pier: EOF
~zod:dojo> pier: work exit: status 0, signal 6

on reboot:

❯ ./piers/zod/.run
~
urbit 3.0
boot: home is /home/mike/piers/zod
disk: loaded epoch 0i109
loom: mapped 2048MB
boot: protected loom
live: mapped: MB/760.184.832
live: loaded: KB/16.384
boot: installed 967 jets
---------------- playback starting ----------------
play: events 152470-152509
allocate: reclaim: half of 3 entries
allocate: reclaim: half of 1 entries
allocate: reclaim: memo cache: empty

bail: meme
home: bailing out
zsh: IOT instruction (core dumped)  ./piers/zod/.run

this was after uploading a 100mb file repeatedly

[joemfb]

Can you meld or run with a larger loom?