ASSERTION FAILED : openj9-openjdk-jdk17/omr/gc/base/MarkingScheme.hpp:70: ((false))

[Afzal-ibm]

16:39:45.137894947 *0x0000000000000000 dg.259 Debug ***** Context change to ee 0x301cc438 *****
16:39:45.137895283 0x0000000000000000 j9mm.76 Event Concurrent background thread activated
16:39:45.139408613 *0x0000000030009200 j9mm.143 Event Concurrent class mark start
16:39:45.145212684 *0x000000003001e000 j9vm.242 Entry >J9SignalAsyncEvent targetThread=0x30009200 handlerKey=2
16:39:45.145213616 0x000000003001e000 j9vm.243 Exit <J9SignalAsyncEvent returning 0
16:39:45.145214098 0x000000003001e000 j9vm.242 Entry >J9SignalAsyncEvent targetThread=0x3000b700 handlerKey=2
16:39:45.145214468 0x000000003001e000 j9vm.243 Exit <J9SignalAsyncEvent returning 0
16:39:45.145215391 0x000000003001e000 j9vm.242 Entry >J9SignalAsyncEvent targetThread=0x30014c00 handlerKey=2
16:39:45.145215802 0x000000003001e000 j9vm.243 Exit <J9SignalAsyncEvent returning 0
16:39:45.145217245 0x000000003001e000 j9vm.242 Entry >J9SignalAsyncEvent targetThread=0x301cb900 handlerKey=2
16:39:45.145217725 0x000000003001e000 j9vm.243 Exit <J9SignalAsyncEvent returning 0
16:39:45.147649987 *0x00000000301cb900 j9mm.621 Event GC Assertion message: Pointer: 0000000000000001 has is not object aligned (to 8 bytes)

16:39:45.147653241 *0x0000000000000000 j9mm.621 Event GC Assertion message: Pointer: 0000000000000001 has is not object aligned (to 8 bytes)

16:39:45.147676180 *0x00000000301cb900 j9mm.141 Assert * ** ASSERTION FAILED ** at /afz/afz/24_04/builds/7.5/jv1_java17_buildv7r5_12170140/openj9-openjdk-jdk17/omr/gc/base/MarkingScheme.hpp:70: ((false))

possible heap corruption or is this due to jdk.internal.misc.Unsafe ?

[Afzal-ibm]

@pshipton @dmitripivkine

[dmitripivkine]

Hi @Afzal-ibm,
This assertion means GC has discovered 0x1 at the place where object pointer expected to be. Based on assertion alone I can not tell is bad value discovered during roots scan (for example O-slot in the java stack) or during of the scan of the object in the heap. In order to investigate we need system dump file or standalone test case to reproduce this problem internally.

[dmitripivkine]

This is internal customer case should not be handled in the open