Some profiles fail to compress.

Whilst experiencing a problem that was caused by [`issues/11`](https://github.com/firefox-devtools/profiler/issues/11#issue-185244795) not yet being implemented, [^3] I discovered that I am unable to submit a profile [^2] for [`bugzilla.mozilla.org/show_bug.cgi?id=2043908`](https://bugzilla.mozilla.org/show_bug.cgi?id=2043908), for I observe: [^1]

[^3]:

[^1]: [`blob/1e84d239338c59b82b27666f714b2750e969d839/locales/en-GB/app.ftl#L682C49-L682C130`](https://github.com/firefox-devtools/profiler/blob/1e84d239338c59b82b27666f714b2750e969d839/locales/en-GB/app.ftl#L682C49-L682C130:~:text=Error%20while%20compressing%2C%20try%20unticking%20some%20tickboxes%20to%20reduce%20the%20profile%20size%2E)

- > https://github.com/firefox-devtools/profiler/blob/1e84d239338c59b82b27666f714b2750e969d839/locales/en-GB/app.ftl#L682

-

~~~MA
20:13:13.451 Error while compressing the profile data out of memory publish.ts:333:17
i publish.ts:333
Kw publish.ts:336
Redux 2
componentDidMount Publish.tsx:85
React 90
Kk scheduler.production.js:151
~~~

I've not even exceeded the default buffer size.

I'd rather that the user be able to access the profile locally, rather than the approach that [`issues/5193`](https://github.com/firefox-devtools/profiler/issues/5193#issue-2641975527) describes being undertaken.

[^2]: [`profiler.firefox.com/from-browser/calltree/?globalTrackOrder=x90x7x0ux4vx3mx6nx1la8x5irjf3oc7x2qs5t6kghebp21x849d&hiddenGlobalTracks=1wtvx1wx3x5x6x8&hiddenLocalTracksByPid=12974-014w7~65456-01~66008-01~66165-01~14141-0~13238-0~13506-0~13409-0~13713-0~13132-0~13577-0~14444-0w3~13534-01~13098-0~13123-0~61755-01~13258-01~14597-0~13219-01~13626-01~13184-0~62187-01~23229-0w2~64652-01~13200-0w2~14499-01~13460-0w2~64443-01~52828-01~38881-01~30626-0~13343-0w2~13663-0~13604-0w2~13304-0w2~13440-0w3~13283-12~14537-0w4~13178-0we~13985-0wc~14978-0wyi&thread=yv&v=16`](https://profiler.firefox.com/from-browser/calltree/?globalTrackOrder=x90x7x0ux4vx3mx6nx1la8x5irjf3oc7x2qs5t6kghebp21x849d&hiddenGlobalTracks=1wtvx1wx3x5x6x8&hiddenLocalTracksByPid=12974-014w7~65456-01~66008-01~66165-01~14141-0~13238-0~13506-0~13409-0~13713-0~13132-0~13577-0~14444-0w3~13534-01~13098-0~13123-0~61755-01~13258-01~14597-0~13219-01~13626-01~13184-0~62187-01~23229-0w2~64652-01~13200-0w2~14499-01~13460-0w2~64443-01~52828-01~38881-01~30626-0~13343-0w2~13663-0~13604-0w2~13304-0w2~13440-0w3~13283-12~14537-0w4~13178-0we~13985-0wc~14978-0wyi&thread=yv&v=16)

#### My Environment

1.

~~~pwsh
#!/usr/bin/env pwsh
rpm -qf (Get-Command firefox-nightly).Source --queryformat @'
Name: %{NAME}
Version: %{VERSION}
Release: %{RELEASE}
Architecture: %{ARCH}
Install Date: %{INSTALLTIME:date}
Size: %{SIZE}
Signature: %{SIGPGP:pgpsig}
Source RPM: %{SOURCERPM}
Build Date: %{BUILDTIME:date}
Build Host: %{BUILDHOST}
Packager: %{PACKAGER}
Vendor: %{VENDOR}
'@ | yq -P
~~~

1.

~~~YAML
Name: firefox-nightly
Version: 154.0a1
Release: 20260624063255
Architecture: x86_64
Install Date: Wed 24 Jun 2026 21:02:52 BST
Size: 390885290
Signature: (none)
Source RPM: firefox-nightly-154.0a1-20260624063255.src.rpm
Build Date: Wed 24 Jun 2026 13:04:52 BST
Build Host: e8559ebc86ac
Packager: (none)
Vendor: Mozilla
~~~

┆Issue is synchronized with this [Jira Task](https://mozilla-hub.atlassian.net/browse/FP-1340)

Start with the compression error at publish.ts:333 and the call from Publish.tsx:85, then inspect the affected profile link and the message in locales/en-GB/app.ftl:682. Reproduce the failure with that profile and trace the publish flow. Done means the affected profile remains accessible locally instead of failing with only the compression error.

Written by the indexing model from the issue text.