<?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: Infinite loading specific to Arc Browser in Databricks Free Edition Help</title>
    <link>https://community.databricks.com/t5/databricks-free-edition-help/infinite-loading-specific-to-arc-browser/m-p/148334#M669</link>
    <description>&lt;P class="p8i6j01 paragraph"&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/182410"&gt;@JIWON&lt;/a&gt;!&lt;/P&gt;
&lt;P class="p8i6j01 paragraph"&gt;Agreed — this is almost certainly an Arc-specific quirk, not Chromium itself. Known Arc pain points match your symptoms so you are not alone!&lt;/P&gt;
&lt;P&gt;We've seen the following fixes come in handy in previous, similar situations:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Clear site data for your workspace in Arc, then hard reload. This often resolves Arc-only infinite loads.&lt;/LI&gt;
&lt;LI&gt;Try a clean Arc profile with no extensions to rule out extension interference/caching oddities.&lt;/LI&gt;
&lt;LI&gt;In DevTools, check if CDN/UI assets (e.g., login.js, databricks-ui-assets) are blocked, zero-byte, or pending; Arc sometimes mishandles these while Chrome is fine.&lt;/LI&gt;
&lt;LI&gt;If device posture/login is in the path, add Local Network Access allowlists in Arc (arc://settings/content/localNetworkAccess) — e.g., auth.community.com, app.community.com; avoid “:443”.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Ultimately - the suggestion is to use Chrome/Safari as a workaround (Arc is less supported internally).&lt;/P&gt;
&lt;P class="p8i6j01 paragraph"&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 13 Feb 2026 14:42:20 GMT</pubDate>
    <dc:creator>sarahbhord</dc:creator>
    <dc:date>2026-02-13T14:42:20Z</dc:date>
    <item>
      <title>Infinite loading specific to Arc Browser</title>
      <link>https://community.databricks.com/t5/databricks-free-edition-help/infinite-loading-specific-to-arc-browser/m-p/142794#M583</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I previously &lt;A href="https://community.databricks.com/t5/databricks-free-edition-help/multiple-ui-pages-stuck-on-infinite-loading-jobs-dag-compute-sql/m-p/140460" target="_blank"&gt;reported issues&lt;/A&gt; where the Databricks Workspace UI (Jobs DAG, Compute, SQL Editor, Notebooks) was stuck on infinite loading.&lt;/P&gt;&lt;P&gt;I previously encountered similar symptons, and at that time, the issue eventually resolved itself spontaneously after a while. &lt;STRONG&gt;However, today the issue is persisiting and has not improved at all.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;After further testing, I've isolated it specifically to the &lt;STRONG&gt;Arc Browser.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Here are my comparison results:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Safari: Works perfectly.&lt;/LI&gt;&lt;LI&gt;Google Chrome: Works perfectly (Version: 143.0.7499.170)&lt;/LI&gt;&lt;LI&gt;Arc Browser: &lt;STRONG&gt;Infinite Loading issues&lt;/STRONG&gt; (Version: v1.126.1 / Chromium Engine: 143.0.7499.170)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;The Problem: Even though both Chrome and Arc are running the exact same Chromium engine version (143.0.7499.170), the Databricks UI fails to load only on Arc. This suggests the issue is not with the Chromium engine itself, but something specific to Arc's implementation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a dedicated Arc user, it is quite disappointing to have to switch browsers just for this workspace issue.&lt;/P&gt;&lt;P&gt;Has anyone else encountered this specific incompatibility with Arc? Any advice or workarounds to make it work on Arc would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2026 01:04:05 GMT</pubDate>
      <guid>https://community.databricks.com/t5/databricks-free-edition-help/infinite-loading-specific-to-arc-browser/m-p/142794#M583</guid>
      <dc:creator>JIWON</dc:creator>
      <dc:date>2026-01-02T01:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: Infinite loading specific to Arc Browser</title>
      <link>https://community.databricks.com/t5/databricks-free-edition-help/infinite-loading-specific-to-arc-browser/m-p/148334#M669</link>
      <description>&lt;P class="p8i6j01 paragraph"&gt;Hey&amp;nbsp;&lt;a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/182410"&gt;@JIWON&lt;/a&gt;!&lt;/P&gt;
&lt;P class="p8i6j01 paragraph"&gt;Agreed — this is almost certainly an Arc-specific quirk, not Chromium itself. Known Arc pain points match your symptoms so you are not alone!&lt;/P&gt;
&lt;P&gt;We've seen the following fixes come in handy in previous, similar situations:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Clear site data for your workspace in Arc, then hard reload. This often resolves Arc-only infinite loads.&lt;/LI&gt;
&lt;LI&gt;Try a clean Arc profile with no extensions to rule out extension interference/caching oddities.&lt;/LI&gt;
&lt;LI&gt;In DevTools, check if CDN/UI assets (e.g., login.js, databricks-ui-assets) are blocked, zero-byte, or pending; Arc sometimes mishandles these while Chrome is fine.&lt;/LI&gt;
&lt;LI&gt;If device posture/login is in the path, add Local Network Access allowlists in Arc (arc://settings/content/localNetworkAccess) — e.g., auth.community.com, app.community.com; avoid “:443”.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;Ultimately - the suggestion is to use Chrome/Safari as a workaround (Arc is less supported internally).&lt;/P&gt;
&lt;P class="p8i6j01 paragraph"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Feb 2026 14:42:20 GMT</pubDate>
      <guid>https://community.databricks.com/t5/databricks-free-edition-help/infinite-loading-specific-to-arc-browser/m-p/148334#M669</guid>
      <dc:creator>sarahbhord</dc:creator>
      <dc:date>2026-02-13T14:42:20Z</dc:date>
    </item>
  </channel>
</rss>

