RFR: 8376970: Shenandoah: Verifier should do basic verification before touching oops
Aleksey Shipilev
shade at openjdk.org
Tue Feb 3 08:45:10 UTC 2026
On Mon, 2 Feb 2026 18:06:33 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:
> Noticed this when working on [JDK-8376749](https://bugs.openjdk.org/browse/JDK-8376749). When Verifier is about to fail on broken oop, it would decode the broken compressed pointer before doing any verification on it. So the end result is that we _at best_ catch the non-verbose assert in shared code in debug builds, or we crash the VM with opaque error in release builds, instead of rich Shenandoah verification failure.
>
> We need to tighten this up, so that Verifier does work properly in these conditions.
>
> Additional testing:
> - [x] Ad-hoc crashes now show proper diagnostics
> - [x] Linux x86_64 server fastdebug, `hotspot_gc_shenandoah`
Thanks for reviews! I think all interested parties have replied, so I am integrating before 24 hours expire.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/29527#issuecomment-3839905109
More information about the shenandoah-dev
mailing list