On Mon, 7 Jul 2025 07:53:24 GMT, Albert Mingkun Yang <ay...@openjdk.org> wrote:
>> Yes. I don't think it is exceeding overhead limit only problem, but OOM and >> heap dump have to be, in a sense of `atomic`. We encountered this problem >> in real production system. > >> but OOM and heap dump have to be, in a sense of atomic > > I see; it can indeed be annoying that heap-dump doesn't capture the intended > snapshot -- a java thread can trigger a gc that changes heap-content. > However, AFAICS, fixing that non-atomic issue requires updating callers of > `report_java_out_of_memory`. Therefore, I am inclined to think it should be > addressed in its own ticket. It's a preexisting issue on master as well, not > sth newly introduced by this PR. Does https://bugs.openjdk.org/browse/JDK-8347833 match the problem you have in mind? ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/25000#discussion_r2189284517
