That may not be how some folks understand the concept of crashing, but it's definitely how most folks understand it, at least insofar as they write software.
1 service instance needs to be able to handle O(1k+) concurrent requests at scale, and a failure in any given request can't impact other in-flight requests. Those failures aren't crashes, and that software isn't crash-only -- using those terms just obfuscates things, and makes everything harder for everyone.