Crash on MacOS 7.3.1 release

[sluongng]

Description of the bug:

I was doing a bazel test and got

Computing main repo mapping:

Server terminated abruptly (error code: 14, error message: 'Socket closed', log file: '/private/var/tmp/_bazel_sluongng/06e573a93bc2d6a9cad4ad41f00b4310/server/jvm.out')

Then this file appeared in my repository with the JVM crash details:

hs_err_pid16796.log

It seems like the crash has something to do with net.starlark.java.eval.MutableStarlarkList

Which category does this issue belong to?

Starlark Interpreter

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

Cannot reliably reproduce.

Which operating system are you running Bazel on?

MacOS

What is the output of bazel info release?

release 7.3.1

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 ?

https://github.com/buildbuddy-io/buildbuddy.git
a3502e0dc89ea019e3bbe682bc9fe7bb1d2c17d8

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

[sluongng]

hs_err_pid11464.log

got another one today

[sluongng]

hs_err_pid48965.log

Got another crash today while on 7.4.0.
I think the new OpenJDK change is applied this time.

cc: @fmeum

[fmeum]

The crash appears to occur on a list that always has 1912 entries and strings such as 14.17.5-linux_amd64 appear in memory. Do you happen to know where this list comes from?