<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Bug on Arhuman's Blog</title><link>https://blog.assad.fr/en/tags/bug/</link><description>Recent content in Bug on Arhuman's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 20 Mar 2026 15:24:26 +0100</lastBuildDate><atom:link href="https://blog.assad.fr/en/tags/bug/index.xml" rel="self" type="application/rss+xml"/><item><title>What if your OOM was not just a memory problem?</title><link>https://blog.assad.fr/en/post/what-if-oom-is-not-only-about-memory/</link><pubDate>Fri, 20 Mar 2026 15:24:26 +0100</pubDate><guid>https://blog.assad.fr/en/post/what-if-oom-is-not-only-about-memory/</guid><description>&lt;p&gt;Sometimes an investigation tells a different story than the one you expected.&lt;/p&gt;
&lt;p&gt;That&amp;rsquo;s what happened to me recently while investigating why a pod was ending up OOMKilled two to three times a day.&lt;/p&gt;
&lt;p&gt;A quick look at the memory of the incriminated pod doesn&amp;rsquo;t show the typical rising curve of a memory leak. I&amp;rsquo;m missing data just before the OOM (because it&amp;rsquo;s always when your metrics system is migrating that this kind of incident happens), but with the day&amp;rsquo;s data, the cause seems to lie elsewhere.&lt;/p&gt;</description></item></channel></rss>