Some Nomad UI XHR requests are blocked by Firefox's default settings (NS_BINDING_ABORTED)

[markasoftware-aqtc]

Nomad version

Nomad v1.9.3

Operating system and Environment details

macOS Sequoia, Firefox 133.0

Issue

While browsing around the Nomad web UI, certain things don't auto-refresh the way they do in Chrome. Looking in the browser dev console, a number of XHR requests seem to fail with NS_BINDING_ABORTED, which I believe means Firefox is internally blocking them. Additionally, at least one request fails with NS_ERROR_OUT_OF_MEMORY (my machine has plenty of memory and taking a memory snapshot indicates that the page is using ~50 MiB of memory, which shouldn't be anywhere near Firefox's per-page limits).

Some basic reading online indicates that NS_BINDING_ABORTED means Firefox is blocking the request for one of any number of reasons. My first guess was that it was being blocked as part of Firefox's anti-tracking features that are enabled by default, but even after adding an anti-tracking exception, the failed requests continue.

Reproduction steps

1. Open Firefox dev console in the Network tab
2. Navigate to the Nomad web UI homepage
3. Click on a job, ideally one with some allocations under it
4. Navigate back to the homepage using the breadcrumbs

Expected Result

All requests should succeed. For example, all requests succeed in Chrome.

Actual Result

A number of requests (when I do this procedure, usually at least 4) fail with NS_BINDING_ABORTED error, and sometimes one will fail with NS_ERROR_OUT_OF_MEMORY also

(confidential job names redacted)

Job file (if appropriate)

N/A

Nomad Server logs (if appropriate)

N/A

Nomad Client logs (if appropriate)

N/A

[tgross]

Hi @markasoftware-aqtc! I'm going to flag this issue for our web UI expert @philrenaud.