`Error in compression worker` being spammed after adding replay integration

[Joshandrews43]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which package are you using?

@sentry/react

SDK Version

7.32.1

Framework Version

17.0.0

Link to Sentry event

https://sentry.io/organizations/after-school-development-llc/issues/3892582226/events/c7a67fbc5cfc467da7f9bd8f57161bbd/?project=5417223&referrer=replay-console%2F

SDK Setup

Sentry.init({
 dsn:
 process.env.SENTRY_DSN,
 integrations: [
 new Integrations.BrowserTracing(),
 new Sentry.Replay({ maskAllText: false, blockAllMedia: false }),
 ],
 tracesSampleRate: 0.5,
 enabled: process.env.NODE_ENV !== 'development',
 release: process.env.REACT_APP_HEROKU_RELEASE_VERSION,
 replaysSessionSampleRate: 0,
 replaysOnErrorSampleRate: 1,
});

Steps to Reproduce

Im not sure if I can reproduce in on my own, but there are 150 events since I launched this yesterday in production.

Also my replaysSessionSampleRate is set to 0, but I am still getting replays recorded with no errors.

Expected Result

Sentry should not be throwing 100's of errors from itself.

Actual Result

[mydea]

Thanks for the report!

Regarding the worker error, we are currently working on a fix for this which should make this error go away (or put better, swallow it). Sorry about the noise! This should not happen. If you keep getting a lot of these errors, as a temporary workaround you can disable compression by setting new Replay({ useCompression: false }).

You can track #6924 for progress on this. I'll let you know when this has been released!

Regarding the recording without errors at all, that's weird. Do you maybe have a link to a replay without an error that we could have a look at?

[Joshandrews43]

Thanks for the report!

Regarding the worker error, we are currently working on a fix for this which should make this error go away (or put better, swallow it). Sorry about the noise! This should not happen. If you keep getting a lot of these errors, as a temporary workaround you can disable compression by setting new Replay({ useCompression: false }).

You can track #6924 for progress on this. I'll let you know when this has been released!

Regarding the recording without errors at all, that's weird. Do you maybe have a link to a replay without an error that we could have a look at?

Hi! Thanks for the info, here is an example replay. Note the sample values are 1 and 0 respectively, so it definitely should not have recorded this.

https://sentry.io/organizations/after-school-development-llc/replays/carline-web:45fc90cdc6b749ba8fe20cfd4591f1d0/?project=5417223&query=duration%3A%3E%3D5&referrer=%2Forganizations%2F%3AorgId%2Freplays%2F&statsPeriod=14d&t_main=console&t_side=tags&yAxis=count%28%29

[mydea]

Thanks!
This seems all correct to me. Just to be clear, you didn't add any beforeSend or addGlobalEventProcessor hooks, did you? Because with the current implementation, these are scenarios that could lead to no errors being attached even though we triggered a replay.

In the future, we want to handle this with a kind of afterSend functionality - this hook functionality is currently work in progress!

[Joshandrews43]

I have neither a beforeSend nor a addGlobalEventProcessor. So you're saying that it is correct as is? What could trigger an replay if my session sample rate is 0 and no errors are thrown?

The reason I ask is because it makes our replay dashboard super cluttered and hard to navigate when I specify we only want errors but ~33-40% of replays have no errors.

[mydea]

Thanks for all the info!
We did some more digging, and we think we found the culprit. Basically, currently a session will be started due to an error. Once the session times out (after 15min of user inactivity, or 60min of activity), we'll renew the session. This shows up as a new replay, which then has no error attached.

This #6948 should fix this issue!

[mydea]

Hey, so we just released 7.34.0 which should fix both of the issues you've been having. Can you give it a try and let me know if the problems are gone?

[Freundschaft]

hhm, i didnt have these issues before, but since 7.34.0 I also get this error

[mydea]

hhm, i didnt have these issues before, but since 7.34.0 I also get this error

Hey, sorry to hear that. Could you provide a full error message, or link to a Sentry event where you have this error (if you're on SAAS)? We should be try-catching the only place in the code where this can really be thrown, but maybe we missed a place somewhere.