Ooo, I also had a graalvm migration bug, where it was corrupting a deep aes256 call which was costing us ~1M dollars a day or so until we figured it out.
Yikes, can you explain a bit more? It sounds like a nightmare to debug.
Yeah, I think it was that an AES function/instructions and some array clearing were getting reordered unsafely, but only under some very specific distributed modes. We were mostly able to get repo after a couple of days, but it was complicated by having a pretty deep stack and the fact that the corrupting change was being canaried out, not released.