RFR: 8329665: fatal error: memory leak: allocating without ResourceMark

[Coleen Phillimore]

On Thu, 4 Apr 2024 16:23:50 GMT, Patricio Chilano Mateo <pchilanomate at openjdk.org> wrote:

> There are two places in Loom code that call f.oops_interpreted_do() to process oops in the stackChunk. Although not obvious this method seem to require to have a ResourceMark on scope and there are several contexts where these two are call where we don't have one. The reason why a ResourceMark is needed is because OopMapCache::compute_one_oop_map() might allocate from the resource area if _mask_size is > 4 * BitsPerWord, which depends on the amount of locals + expression stack of the corresponding method. But ~InterpreterOopMap already checks if the _bit_mask was allocated in the resource area and in that case it will free it. So the ResourceMark is not strictly needed except that in debug mode we will actually hit the assert if there is not one in scope when trying to allocate the _bit_mask.
> 
> Thanks,
> Patricio

src/hotspot/share/runtime/frame.cpp line 888:

> 886:   assert(is_interpreted_frame(), "Not an interpreted frame");
> 887:   Thread *thread = Thread::current();
> 888:   DEBUG_ONLY(ResourceMark rm(thread);) // ~InterpreterOopMap already handles possible deallocation of bitmask

I don't like that this is in debug mode only either.  We have the current thread so that's a part of the cost of ResourceMark (or historically been the cost).  I wonder if this "optimization" can be observed.  I'd rather the explicit resource allocation deletion be removed also, since this is surprising.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/18632#discussion_r1554272912