<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why does browser.tabs.unloadOnLowMemory set false by default? in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/why-does-browser-tabs-unloadonlowmemory-set-false-by-default/m-p/45678#M16463</link>
    <description>&lt;P&gt;This is pretty late but hopefully still useful to you.&lt;/P&gt;&lt;P&gt;According to gsvelto,&amp;nbsp;&lt;A href="https://news.ycombinator.com/item?id=33706117" target="_self"&gt;one of the developers&lt;/A&gt;, it is because the detection of low memory doesn't work:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;Yes it does, we've disabled tab unloading on Linux because low-memory detection just didn't work. We will re-enabled it sometimes down the line but only to avoid swap, not crashes. The OOM killer does already a good job with this change and we feel no need to do anything further (besides optimizing memory usage, but that's system-agnostic).&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 25 Nov 2023 21:03:13 GMT</pubDate>
    <dc:creator>blankuser</dc:creator>
    <dc:date>2023-11-25T21:03:13Z</dc:date>
    <item>
      <title>Why does browser.tabs.unloadOnLowMemory set false by default?</title>
      <link>https://connect.mozilla.org/t5/discussions/why-does-browser-tabs-unloadonlowmemory-set-false-by-default/m-p/18109#M7973</link>
      <description>&lt;P&gt;In my environment (Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0), the &lt;A href="https://support.mozilla.org/en-US/kb/unload-inactive-tabs-save-system-memory-firefox" target="_self"&gt;feature to unload inactive tabs&lt;/A&gt; was disabled by default. Is there a reason for this, such as a significant performance impact?&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2022 00:23:59 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/why-does-browser-tabs-unloadonlowmemory-set-false-by-default/m-p/18109#M7973</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-11-02T00:23:59Z</dc:date>
    </item>
    <item>
      <title>Re: Why does browser.tabs.unloadOnLowMemory set false by default?</title>
      <link>https://connect.mozilla.org/t5/discussions/why-does-browser-tabs-unloadonlowmemory-set-false-by-default/m-p/45678#M16463</link>
      <description>&lt;P&gt;This is pretty late but hopefully still useful to you.&lt;/P&gt;&lt;P&gt;According to gsvelto,&amp;nbsp;&lt;A href="https://news.ycombinator.com/item?id=33706117" target="_self"&gt;one of the developers&lt;/A&gt;, it is because the detection of low memory doesn't work:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;Yes it does, we've disabled tab unloading on Linux because low-memory detection just didn't work. We will re-enabled it sometimes down the line but only to avoid swap, not crashes. The OOM killer does already a good job with this change and we feel no need to do anything further (besides optimizing memory usage, but that's system-agnostic).&lt;BR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 25 Nov 2023 21:03:13 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/why-does-browser-tabs-unloadonlowmemory-set-false-by-default/m-p/45678#M16463</guid>
      <dc:creator>blankuser</dc:creator>
      <dc:date>2023-11-25T21:03:13Z</dc:date>
    </item>
  </channel>
</rss>

