Sudden spike in the number of sessions per user in newer version of electron sdk

[gid-sentry]

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)

Electron SDK Version

4.22.0

Electron Version

27.2.0

What platform are you using?

None

Link to Sentry event

https://jupiter-ct.sentry.io/releases/desktop%4024.2.15%2BRCAppDesktop/?chart=sessionCount&issuesType=unhandled&pageEnd=2024-04-19T11%3A00%3A00&pageStart=2024-04-14T23%3A29%3A35&project=1430058

Steps to Reproduce

Update to sdk version 4.22.0, have max Minidumps per session set to 8.

Expected Result

Same rough number of sessions to users

Actual Result

Significantly more sessions per user

[gid-sentry]

Does not look like version 4.24 has updates that would affect this functionality as it seems like dependency updates for the javascript sdk + some replay related fixes.

[gid-sentry]

Internal Case Doc: https://www.notion.so/sentry/096c7ce2987a4e598ca234c82a222853?v=693bea0c95b54382bb9523ab05711127&p=98b0d84eada9433fa8d313b613e9324c&pm=s

[AlbertInRC]

Maybe you could check how the sessions were uploaded from a minimum group of users.

[smeubank]

hi @timfish fyi the init looks something like this, would you mind having a look if anything is suspicious here, I am not familiar with this feature, or why there are 2 variants of minidump 😅

import * as Sentry from "@sentry/electron";

Sentry.init({
  dsn: SENTRY_DSN,
  ….
  integrations: [
    new Sentry.Integrations.MainProcessSession({ sendOnCreate: true }),
    new Sentry.Integrations.ElectronMinidump()
  ],
 …..
});

[timfish]

That init code looks fine. The ElectronMinidump integrations uses Electrons built in native uploader. It's potentially more reliable but lacks the ability to include full context like our custom uploader in the SentryMinidump integration.

Above, both 4.24 and 4.22.0 are mentioned. Which version worked ok and which version started to cause the issue?

[smeubank]

After integrating the new Sentry SDK 4.22.0 with the following feature, the Crash Free Sessions rate becomes a lot better than before: [*](#830)

• generate maximum 10 sentry errors for a single session by default

We find that a minimum # of users will create lots of sessions.  It blocks our sign off for a new release.  Could you pls help us understand why?  Is it because of a single user upload too many sessions?

I think the mention of 4.24 is red herring, when they moved to 4.22 the issue started, and it appears there is no benefit from 4.24

[timfish]

Assuming they were on 4.21.0 before...

The Electron SDK 4.21.0 to 4.22.0 diff is minimal:
4.21.0...4.22.0

The JavaScript SDK changes from v7.107.0 to v7.109.0 were more extensive but I'm not aware of any changes to sessions:
getsentry/sentry-javascript@7.107.0...7.109.0

[timfish]

Did they end up reverting to the previous version or are they still seeing excessive sessions?

[timfish]

When this issue closes, 5.4.0 will be published to npm. This has a fix for multiple sessions being recorded when there are multiple renderer crashes in a single session. Let us know if this fixes this issue!