tools/java/java stack trace
// javanew

java stack trace

colorize and navigate java exceptions and stack traces

  // browser 
// beautified output appears here
// prohistory syncpro·bulk analysis via APIproupgrade →

// related tools

json → javagenerate java pojos or records from jsonjava decompilerdecompile .class and .jar files back to java sourcemaven ↔ gradleconvert dependencies between maven and gradle dsl

// about this tool

Java stack traces are dense walls of text mixing your own code with dozens of library frames from Spring, Hibernate, Netty, and the JDK itself. This tool parses the raw trace and renders it with syntax coloring: exceptions in red, Caused by chains in orange, your own frames highlighted, and library noise dimmed. The status bar shows the exception class and how many of the frames are your code.

// when to use

  • Quickly spot which of your classes caused an exception among library noise
  • Understand a multi-level Caused by chain in a single glance
  • Share a clean, readable trace with a teammate in a PR comment
  • Identify the root cause when a NullPointerException is buried under 60 Spring frames

// faq

How does it decide which frames are "mine"?
Frames starting with known library prefixes — java.*, javax.*, org.springframework.*, org.hibernate.*, io.netty.*, kotlin.*, and 10+ more — are treated as library code and dimmed. Everything else is treated as your code and highlighted. The list covers the most common Java ecosystems.
Is the trace sent anywhere?
No. All parsing and coloring happens in your browser with JavaScript. Your stack traces, which often contain class and method names from internal code, never leave the tab.
// history
Pro Cloud Sync — upgrade
no operations yet