Identify how errors without a stack trace happen

For context: https://github.com/getsentry/sentry-javascript/discussions/5334

For this to be resolved, we should identify how errors without stack traces happen, and how to reproduce them.

• Investigate v8 source code to see when stack trace is attached
• Query sentry events to see JavaScript errors without stack trace
• Test fetch scenarios to check stack trace
• Analyze errors across browsers

[yordis]

As far as I can tell from speaking to @AbhiPrasad the issue is happening with Safari and Chrome; therefore, they are two different JavaScript runtimes.

I would research if they share the same message,

If so, I would focus on understanding if they rely on some Operation System-level components to do network in the case of fetch or something similar.

Otherwise, it will require investigating V8 and Safari Webkit to see where they are not giving enough insides.

Also, I will assume that such an issue comes from internal components so that is why not much information is given, which leads me to maybe research how the Consoles are now giving you nice linking between async operations, it may be the case that there is a way to add some metadata or that they are doing it at a layer that we cant control and not much we can do other than loop-in Browser vendors.

[vladanpaunovic]

We validated that this is not big of a problem so I am closing this until there this problem becomes big enough.