captureException with POJO shows Sentry internal as top stack frame

[Dodie324]

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 SDK are you using?

@sentry/react

SDK Version

7.54.0

Framework Version

React 18

Link to Sentry event

https://afresh.sentry.io/issues/4232470254/?project=5540748&referrer=slack

SDK Setup

  Sentry.init({
    dsn: vars.sentryDsn,
    environment: vars.environment,
    release: `${vars.buildNum} (${vars.buildHash})`,
  })

  Sentry.configureScope((scope) => {
    scope.setExtra('actor', 'web-client')
    scope.setTag('client_version', vars.appVersion)
  })

Steps to Reproduce

After upgrading @sentry/react from v6.11 -> v7.54, the source map where the exception gets triggered is different from what it typically is, and as a result, generates a weird issue title when logged to our dashboard. Am I missing something in the update?

v.6.11

v.7.54

Expected Result

I'd expect logging to remain the same

Actual Result

Source maps appear to be wrong, and is generates a weird title in the Issues dashboard

[mydea]

High there,

I think the actual, underlying problem here is that we are not stripping the captureException stuff from the stack trace. This should not be the top frame in the first place! I'll look into it if/how we can strip this away - FYI the cause for this is that we are creating a synthetic exception to get the stack trace, but need to remove this "synthetic" frame from the top.

[mydea]

Note: I created a new issue with more details & investigation stuff to not clutter this issue: #8396