<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body>
    <br>
    <div class="moz-forward-container"><br>
      <br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0" cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>RFO: a tool to analyze HotSpot fatal error logs</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Thu, 11 Apr 2024 18:05:44 +0400</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td>Maxim Kartashev <a class="moz-txt-link-rfc2396E" href="mailto:maxim.kartashev@jetbrains.com"><maxim.kartashev@jetbrains.com></a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:discuss@openjdk.org">discuss@openjdk.org</a>, <a class="moz-txt-link-abbreviated" href="mailto:hotspot-dev@openjdk.org">hotspot-dev@openjdk.org</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      
      <div dir="ltr">
        <div>Hello,</div>
        <div><br>
        </div>
        <div>I am writing to inquire about the potential interest of the
          people involved in inspecting HotSpot crashes in a tool aimed
          at facilitating that inspection. <br>
        </div>
        <div><br>
        </div>
        <div>We at JetBrains have developed an internal plugin that
          helps both with filtering through dozens of reports quickly in
          order to find a pattern and for diving deep into a particular
          crash. In addition to the "standard" features such as syntax
          highlighting, folding, and structural navigation, it will </div>
        <div>* highlight potential problems such as overloaded CPU, low
          physical memory, the presence of OOME in the recent
          exceptions, LD_LIBRARY_PATH being set, etc,</div>
        <div>* generate an "executive summary" for a high-level
          overview, for example, by front-line support,<br>
        </div>
        <div>* pop up a tooltip for any recognized address describing
          its origin (for example, if it belongs to some thread's stack,
          the Java heap, a register, or a memory-mapped region),</div>
        <div>* provide the ability to highlight all addresses "near" the
          selected address, including registers, threads, and
          memory-mapped regions.</div>
        <div><br>
        </div>
        <div>If there is sufficient interest in creating a public and/or
          open-source variant of this internal plugin, I will pitch the
          idea to my employer. It shouldn't be too much work to create a
          public version.</div>
        <div><br>
        </div>
        <div>Kind regards,</div>
        <div>Maxim.<br>
        </div>
        <div><br>
        </div>
        <div>References:</div>
        <div>* <a href="https://docs.oracle.com/javase/10/troubleshoot/fatal-error-log.htm" moz-do-not-send="true" class="moz-txt-link-freetext">https://docs.oracle.com/javase/10/troubleshoot/fatal-error-log.htm</a></div>
        <div><br>
        </div>
      </div>
    </div>
  </body>
</html>