Tim Fish

I haven't seen this happen myself but I will be investigating it and spending time trying to fix it. if you're seeing hanging issues caused by this I would avoid...

If you're using a bundler you'll likely need to import differently for the main/renderer: https://docs.sentry.io/platforms/javascript/guides/electron/#bundler-configuration This will become the default in the next major version.

Ah sorry I understand the issue now. This `dynamicRequire` is used to workaround node compatibility issues but appears to cause issues with webpack.

Removing use of `dynamicRequire` is a breaking change and has been removed in the next major version (v5) which is currently being worked on.

There is a [beta available](https://github.com/getsentry/sentry-electron/releases/tag/5.0.0-beta.0) of v5 of the Electron SDK which uses v8 of the JavaScript SDKs. `dynamicRequire` is no longer used in this version.

What typically causes `DumpWithoutCrashing` minidumps? I assumed these were caused by manually triggering a minidump with the debugger attached?

It looks like it might be a means for Chromium to collect minidumps for specific things that they're trying to debug and get more information for and these shouldn't make...

The Electron SDK uses the node SDK for the main process and browser SDK for the renderers. Importing from `@sentry/electron` can often work but bundlers can cause the wrong entry...

The Electron SDK is designed to work in Electron apps where you control the full app code. Figma is an Electron app but it looks like Figma plugins have their...

It might also be worth hooking it up to the [`page-title-updated`](https://electron.atom.io/docs/api/browser-window/#event-page-title-updated) event as then the title text will keep updated and will match what's displayed in the titlebar in Linux...