Omit Object#wait0 in ThreadUtils slow interrupt culprit selection. In OpenJDK 21+, java.lang.Object.wait() calls the native wait0() method. ThreadUtils.warnAboutSlowInterrupt only checked for method name "wait", causing threads waiting on Object monitors to not be recognized as waiting. Because the main server thread has a deep stack trace, it was incorrectly selected as the longest active stack trace during slow interrupts. Also add a null-safe fallback if all threads in the JVM are waiting or parked. PiperOrigin-RevId: 972151587 Change-Id: I903441ed3d4bbec44a5e4bfbb964232ade1cc793
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
