<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging on Mi&amp;Bee Blog</title><link>/en/tags/debugging/</link><description>Recent content in Debugging on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Tue, 16 Jan 2018 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/debugging/rss.xml" rel="self" type="application/rss+xml"/><item><title>JVM Performance Tuning and Off-Heap Memory Leak Troubleshooting in Practice</title><link>/en/archives/02-jvm-debug/</link><pubDate>Tue, 16 Jan 2018 00:00:00 +0000</pubDate><guid>/en/archives/02-jvm-debug/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;JVM performance tuning and memory issue troubleshooting have always been significant challenges for Java developers. This article starts from the three core goals of GC tuning and combines them with a real-world off-heap memory leak investigation case to provide a systematic approach to performance tuning and practical troubleshooting methods.&lt;/p&gt;
&lt;p&gt;In complex distributed systems, memory issues are often the hardest to diagnose. Off-heap memory leaks in particular, occurring outside the JVM heap, are difficult to detect with conventional GC monitoring tools and can easily cause systems to crash suddenly in production environments. This article shares a complete off-heap memory leak investigation process, hoping to provide valuable reference for readers.&lt;/p&gt;</description></item></channel></rss>