<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SudarshanTechLabs Blog: Memory Leaks</title>
    <link>https://sudarshantechlabs.com/blog/tag/memory-leaks</link>
    <description>Posts tagged Memory Leaks from SudarshanTechLabs.</description>
    <language>en-us</language>
    <lastBuildDate>Sat, 11 Jul 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://sudarshantechlabs.com/blog/tag/memory-leaks/feed.xml" rel="self" type="application/rss+xml" />
    <managingEditor>support@sudarshantechlabs.com (Sudarshan Chaudhari)</managingEditor>
    <webMaster>support@sudarshantechlabs.com (Sudarshan Chaudhari)</webMaster>
    <item>
      <title>Debugging Memory Leaks in Android With LeakCanary</title>
      <link>https://sudarshantechlabs.com/blog/debugging-memory-leaks-android-leakcanary</link>
      <guid isPermaLink="true">https://sudarshantechlabs.com/blog/debugging-memory-leaks-android-leakcanary</guid>
      <description>Memory leaks rarely crash on the first screen — they crash users three navigations deep. Here&apos;s the LeakCanary workflow I use to catch the common Android leak sources before they hit production. · 5 min read</description>
      <pubDate>Sat, 11 Jul 2026 00:00:00 GMT</pubDate>
      <category>Android</category>
      <category>Memory Leaks</category>
      <category>LeakCanary</category>
      <category>Debugging</category>
      <category>Performance</category>
      <enclosure url="https://sudarshantechlabs.com/og-image.png" type="image/png" length="0"/>
    </item>
  </channel>
</rss>