Menu

SIGILL on Startup: How the JDK AOT Cache Crashed Axelix in Docker
πŸ“°

SIGILL on Startup: How the JDK AOT Cache Crashed Axelix in Docker

DEV Community: dockerΒ·Sergei CherkasovΒ·10 days ago
#P7AqHU7p
#devtodocker#devto#dev#cache#code
Reading 0:00
15s threshold

Author: Artemiy Degtyarev

Imagine you are deploying an open source Java application in Docker. You pull the image, run it, and before the first

log line appears, the JVM dies with this:

# A fatal error has been detected by the Java Runtime Environment: # # SIGILL (0x4) at pc=..., pid=1, tid=... # # Problematic frame: # v ~AdapterBlob

Enter fullscreen mode

Exit fullscreen mode

That is exactly what happened to some users of Axelix when they started Axelix

Master. SIGILL means illegal instruction : the CPU was asked to execute an instruction it does not support. That is

not something you expect from a Java application. Java is supposed to be "write once, run anywhere", and bytecode does not

contain CPU instructions.

We investigated it, fixed it, and wrote this article about it. It is a good story about a new JVM feature, the AOT

cache, and a small detail of its design that turned out to matter a lot for anyone who ships a pre-built Docker image.

What we saw

The bug was reported as #1744 .…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.