Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

100% CPU when adding renderer reporting #118

Closed
jondot opened this issue Sep 24, 2018 · 3 comments
Closed

100% CPU when adding renderer reporting #118

jondot opened this issue Sep 24, 2018 · 3 comments
Assignees

Comments

@jondot
Copy link

jondot commented Sep 24, 2018

Hi,
Not sure how to give you a self-contained example, but I'm having a case where renderer process is stuck 100% cpu when adding integration into renderer process and entire app is unresponsive, nor have access to dev toos. main process works fine and reports crashes well.

@HazAT
Copy link
Member

HazAT commented Sep 25, 2018

What version are you using?
How does Sentry.init look like / what calls are you making to Sentry.?

@HazAT HazAT self-assigned this Sep 25, 2018
@jondot
Copy link
Author

jondot commented Sep 25, 2018

Actually exactly like the demo states. simply copy/paste the code snippet.
I did another experiment as well - just require the library, and then after app loads, open inspector, and issue the init manually through developer console, get a freeze after 10 sec.

@timfish
Copy link
Collaborator

timfish commented Feb 16, 2022

We have just released v3.0.0 of the SDK which includes a lot of changes and improvements since this issue was opened.

If you can still reproduce this with v3, please open a new issue and I'll look into it.

@timfish timfish closed this as completed Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants