<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Chrome on Asadbek Kurbonov</title><link>/tags/chrome/</link><description>Recent content in Chrome on Asadbek Kurbonov</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 15 Jul 2026 13:45:00 +0200</lastBuildDate><atom:link href="/tags/chrome/index.xml" rel="self" type="application/rss+xml"/><item><title>Facebook Loaded Itself to Death and Almost Took My Machine With It</title><link>/posts/facebook-crash-meta-ai-rush/</link><pubDate>Wed, 15 Jul 2026 13:45:00 +0200</pubDate><guid>/posts/facebook-crash-meta-ai-rush/</guid><description>&lt;p>I almost don&amp;rsquo;t use facebook, but recently, for its marketplace I had to.&lt;/p>
&lt;p>It happened several times that, the landing page silently leaked memory, and at the end killed by earlyoom.&lt;/p>
&lt;p>The tab opened &lt;code>facebook.com/?_rdr&lt;/code> and then just&amp;hellip; sat there. The little logo kept spinning, and spinning, till the underlying process was killed.&lt;/p>
&lt;p>&lt;img alt="Facebook stuck on its loading logo" loading="lazy" src="../../photos/fb-loading.png">&lt;/p>
&lt;p>I pulled up the system monitor. 15.3 GB of 16 GB of RAM is occupied. Swap half full.&lt;/p></description></item></channel></rss>