[8.2.0] Bazel server terminated abruptly

### Description of the bug:

One of our CI jobs recently had a server terminated abruptly exception when running a `bazel build //...`

### Which category does this issue belong to?

Core

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

I'm not sure how to reproduce this issue and it's the first time this has happened to us in 8.2.0 over a lot of builds.

I've attached the `.ips` for the Java process during the crash.

[java-2025-05-17-173256.ips.zip](https://github.com/user-attachments/files/20265973/java-2025-05-17-173256.ips.zip)

### Which operating system are you running Bazel on?

macOS 15.5

### What is the output of `bazel info release`?

8.2.0

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

```text

```

### If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

_No response_

### Have you found anything relevant by searching the web?

_No response_

### Any other information, logs, or outputs that you want to share?

_No response_

Start with the attached java-2025-05-17-173256.ips.zip and the reported bazel build //... invocation on macOS 15.5 with Bazel 8.2.0. Determine why the Bazel server terminated abruptly and document a reproducible failure or a confirmed cause; the issue provides no named source file or failing test.

Written by the indexing model from the issue text.