-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bazel server crashing abruptly in 7.4+ #24389
Comments
Do you still have the file |
Another JVM crash on macOS that may or may not be related: #23497 |
Unfortunately we don't collect these right now but I'm going to start doing that soon and report back once we get a log to share. |
It wasn't, but if this issue really only shows up in 7.4, then that commit may actually be what caused it. I haven't checked whether the JDK can be updated further. |
On our side we see consistent stream of SIGBUS/SIGSEGV on 7.2 running on Macs.
or
|
Cc @cushon |
I would try using the latest JDK update release and see if it still reproduces. If it does, and there's a repro, it would be good to report to https://bugreport.java.com/bugreport/crash.jsp |
@bazel-io fork 8.0.0 |
Work towards bazelbuild#23497 Work towards bazelbuild#24389
Tried to update to java to zulu 21.38.21 in our fork (on top of 7.2.1)
|
Work towards bazelbuild#23497 Work towards bazelbuild#24389 Closes bazelbuild#24431. PiperOrigin-RevId: 698846634 Change-Id: I3fb2d46597b225833a918af9731665bb276322dd
Work towards #23497 Work towards #24389 Closes #24431. PiperOrigin-RevId: 698846634 Change-Id: I3fb2d46597b225833a918af9731665bb276322dd Commit 27a5e45 Co-authored-by: Fabian Meumertzheim <[email protected]>
Does this still happen with Bazel 8.0.0 rc4? |
@meteorcloudy We can't test with Bazel 8 for a while I imagine, there are few rule breakages that must be fixed. Would it be possible to create a Bazel 7 release for this if we think it fixes the crash? |
@luispadron Unfortunately, we are not planning 7.5 yet |
@meteorcloudy is there some workaround for folks on Bazel 7? We can't upgrade very easily to Bazel 8 and were seeing these crashes pretty frequently |
@iancha1992 Let's start the 7.5 release |
@bazel-io fork 7.5.0 |
Work towards bazelbuild#23497 Work towards bazelbuild#24389 Closes bazelbuild#24431. PiperOrigin-RevId: 698846634 Change-Id: I3fb2d46597b225833a918af9731665bb276322dd
Description of the bug:
Since upgrading to 7.4.0 and subsequently 7.4.1 we've been hit by a server crash during random CI (and local) builds:
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I have not found a way to reliably reproduce this issue but were seeing about 1-3 of these per day on our ~300 machine CI fleet.
Which operating system are you running Bazel on?
macOS
What is the output of
bazel info release
?7.4.1
If
bazel info release
returnsdevelopment 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
?No response
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?
There was a GC threading issue in 7.4.0 that was also causing a server crash but that was fixed in 7.4.1 so this might be another case of that issue or something new entirely. I do not see any
Any other information, logs, or outputs that you want to share?
Attached are the Bazel server JVM log from the build it terminated on along with the .ips file generated from the crash.
jvm_logs_and_ips.zip
The text was updated successfully, but these errors were encountered: