[Stack Traces] Filename prepended with "async " causes issues

[souredoutlook]

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? If you use the CDN bundles, please specify the exact bundle (e.g. bundle.tracing.min.js) in your SDK setup.

@sentry/browser

SDK Version

latest

Framework Version

browser frameworks

Link to Sentry event

No response

SDK Setup

n/a

Steps to Reproduce

Please see attached Zendesk tickets for more details

https://sentry.zendesk.com/agent/tickets/79456
https://sentry.zendesk.com/agent/tickets/78491

1. SDK captures an error
2. Stack trace frame is parsed, filename includes "async ..."
3. When Sentry attempts to resolve sourcemaps or fetch source context this fails because of the prepended string "async "

In our Node.js SDK we already handle this:

sentry-javascript/packages/utils/src/stacktrace.ts

Line 115 in 17db8e2

const FULL_MATCH = /at (?:async )?(?:(.+?)\s+\()?(?:(.+):(\d+):(\d+)?|([^)]+))\)?/;

Expected Result

We parse the line of the stack trace and make it Sentry compatible

Actual Result

See the following processing error:

source code was not found (the given url includes "async https://....")

---

cc @AbhiPrasad

[AbhiPrasad]

Some stacktraces with PII removed:

Error: Forbidden resource
  at handlePotentialError(webpack://application-name/../path/to/file.js:32:13)
  at ApiMethods.get(webpack://application-name/../path/to/file.js:119:14)
  at this.get(webpack://application-name/../path/to/file.js:6:54)
  at ? (async https://another-app.com/dist/bundle.12345.js:1:125524)
  at processQuery(webpack://application-name/../path/to/file.js:51:11)

Specifically the problematic frame is async https://https://another-app.com/dist/bundle.12345.js

[timfish]

Nasty, async is in a different position to node.js!

I suspect this might be caused by the fact that https://another-app.com/dist/bundle.12345.js was loaded asynchronously via await import(). Chrome hasn't previously tagged regular async frames like this 🤔