Use `top -H -p ` to find the hot native thread ID, convert it to hex (`printf "%x"`), take a `jstack ` dump, and search for that hex ID as `nid=0x...` in the dump — its stack trace shows the exact method spinning the CPU.

advancedJVM Internals & Memory

Your Java process consumes 100% CPU — walk through diagnosing exactly which thread and method is responsible.

Use `top -H -p <pid>` to find the hot native thread ID, convert it to hex (`printf "%x"`), take a `jstack <pid>` dump, and search for that hex ID as `nid=0x...` in the dump — its stack trace shows the exact method spinning the CPU.

Ready to master this question?

Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.

Next Step

Continue to What does jcmd VM.native_memory reveal that a heap dump cannot? →← Back to all Core Java questions