You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jvmStats catches Exception. It should be catching Exception|java.lang.InternalError. As is noted in the comment in the code, MemoryPoolMXBean throws InternalError, and InternalError is not derived from Exception:
} catch (Exceptionex) {
/* ignore some JVMs might barf here with: * java.lang.InternalError: Memory Pool not found * we just omit the pool in that case!*/
}
The text was updated successfully, but these errors were encountered:
Are you seeing this in practice? I think this is only a stale comment from when we use to catch throwable in the entire codebase. We have removed that, we do not catch fatal errors that we can not recover from. The Javadocs for MemoryPoolMXBean do not document an InternalError.
Relates to #95710. We've seen that InternalError at least twice in our CI system (out of probably tens of thousands of runs). So I've put in a catch for the InternalError.
jvmStats catches Exception. It should be catching Exception|java.lang.InternalError. As is noted in the comment in the code, MemoryPoolMXBean throws InternalError, and InternalError is not derived from Exception:
The text was updated successfully, but these errors were encountered: