RFR: 8347463: jdk/jfr/threading/TestManyVirtualThreads.java crashes with  assert(oopDesc::is_oop_or_null(val)) [v11]
    Roberto Castañeda Lozano 
    rcastanedalo at openjdk.org
       
    Tue Oct 28 09:50:50 UTC 2025
    
    
  
On Tue, 28 Oct 2025 09:39:05 GMT, Anton Seoane Ampudia <aseoane at openjdk.org> wrote:
>> This PR introduces a fix for a intermittent assert crash due to a non-oop found in the stack when deoptimizing.
>> 
>> The `inline_native_GetEventWriter` JFR intrinsic performs a call into the runtime, which can safepoint, to write a checkpoint for the vthread. This call returns a global handle (`jobject`) that then gets resolved to a raw oop.
>> 
>> However, the corresponding `jfr_write_checkpoint_Type` does not set any return, modelling the call as `void`. If a safepoint hits in the small window after the stub returns but before the writer oop is used, and the GC moves the object in that window, the deoptimization path cannot resolve a handle that it never recorded, leading to the subsequent crash.
>> 
>> An IR Framework test is introduced to exercise the error explicitly. Additionally, related documentation in form of comments in the appropriate file (`runtime.hpp`) is added to hopefully prevent similar cases in the future.
>> 
>> **Testing:** passes tiers 1-5
>
> Anton Seoane Ampudia has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Rename class
test/hotspot/jtreg/compiler/intrinsics/TestReturnOopSetForJFRWriteCheckpoint.java line 38:
> 36:  * @requires vm.hasJFR
> 37:  * @library /test/lib /
> 38:  * @run driver compiler.intrinsics.TestReturnsOopSetForJFRWriteCheckpoint
You will have to update this line as well after the class name change.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/27913#discussion_r2468766731
    
    
More information about the hotspot-compiler-dev
mailing list