an I/O object used from a request other than the one that created it
more outbound fetches than the invocation is allowed
the isolate went over its memory limit between invocations, so the platform named it
the storage layer reset the object, which follows a memory kill
CPU or wall-clock
an output gate failure, which means a write did not commit
thrown with no message and no stack.
The shape of an isolate memory kill inside one invocation (four fresh sites, cpuTime
2,213-4,944 ms); folding it into other would hide it.
the classes worth telling apart; anything else is
other, a message-less throw issilent