(for posterity, any time we've encountered this, it was because some test or user code was running System.exit in some codepath)