Skip to content

Missing wasm stack trace frames when using safari browser #9968

Closed as not planned
Closed as not planned

Description

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/wasm

SDK Version

7.89.0

Framework Version

No response

Link to Sentry event

No response

SDK Setup

    const options: Sentry.BrowserOptions = {
        dsn: environment.sentryDsn,
        // eslint-disable-next-line no-process-env
        release: process.env.COMMIT_TAG || process.env.COMMIT_ID || 'unknown',
        integrations: [new WasmIntegration()],
        maxBreadcrumbs: 100,
        sampleRate: 1,
        autoSessionTracking: false,
        beforeSend: async (event, hint) => {
            if (!sentryEnabled) {
                return null
            }
            // set handled to false for all exceptions
            event.exception?.values?.forEach((value) => {
                if (value.mechanism !== undefined) {
                    value.mechanism.handled = false
                } else {
                    ;(value.mechanism as any) = { handled: false }
                }
            })
            if (!event.tags) {
                event.tags = {}
            }
            event.tags.clientType = MetricCollector.getClientType()
            return event
        },
        ignoreErrors: [
            'Failed to fetch',
            /^RequestFailed.*/,
            'TimeoutError: Transaction timed out due to inactivity.',
            /^Request timed out.*/,
            /^Network Error.*/,
            /.*chrome-extension.*/,
        ],
    }

Steps to Reproduce

I raise the same C++ exception from wasm, and the stack trace frames sent from Safari is much shorter than the frames from Firefox/Chrome. Especially, the wasm-function frames are all missing, making it unable to debug C++ using stacktrace.

I'm using the same wasm and same react dev server to trigger the event, the only difference is the browser. The Safari version I'm using is 17.2 (19617.1.17.11.9). The same issue also occurs when using mobile safari.

Expected Result

Frames in Firefox 120.0.1(https://wukong-1o.sentry.io/issues/4744058561/):
图片

Actual Result

Frames in Safari 17.2(https://wukong-1o.sentry.io/issues/4744210387):
图片
The error message is also different.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    • Status

      Waiting for: Community

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions