SDK delays the electron ready event by ~500ms
See original GitHub issueVersions + Platform
- SDK version -
@sentry/electron@v3.0.0
- Electron version -
electron@v16.0.6
- Platform -
Windows & macOS & Linux
Description
As the title says, when calling init
from @sentry/electron/main
the Electron’s ready
event is delayed by approximately 500ms.
I’m on a Mac mini (2018) 3,2GHz 6-Core Intel Core i7 with 32GB of RAM.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8
Top Results From Across the Web
API to enable/disable a window #8415 - electron ... - GitHub
The time between new BrowserWindow(...) and Event: 'ready-to-show' takes quite long time (cca 500ms) during which an user can take an action.
Read more >Dealing with slow Electron startup - javascript - Stack Overflow
60 ms: app ready event is triggered; we create a window using new BrowserWindow(); 170 ms: a blank window appears on the screen;...
Read more >app | Electron
Emitted when the application has finished basic startup. On Windows and Linux, the will-finish-launching event is the same as the ready event; on...
Read more >All the Electron Docs! | Electron
Event : 'ready'. Returns: launchInfo Object macOS. Emitted when Electron has finished initializing. On macOS, launchInfo holds the userInfo of the ...
Read more >Loading Plugin - Quasar Framework
Loading uses a delay (500ms) to display itself so that quick operations won't make the screen flicker. This happens by showing and then...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for the report. I’ll do some profiling and track it down!
@toxik has sent me a CPU profile and it looks like the Electron
crashReporter.start()
call takes 500ms to return on macOS.You can avoid this for now by disabling native crash reporting which can be achieved by removing the
SentryMinidump
integration.I’ve reported this issue to Electron since this is a large regression between Electron v11 to v12: https://github.com/electron/electron/issues/33072