-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Infinite loop #1801
Comments
in my case this happens if react application in iframe with django grappelli |
I have never seen this issue prior to version 4.4.2. My sentry project has a very clear transition to having a circular structor issue once 4.4.2 was released in my app. I'm reverting to 4.4.1 for now |
Fixed in 4.5.0, everything is guarded for circular references now. Cheers! |
Memory crash remains in 4.5.1 for me. Original error:
|
I get the same error! |
It seems that some really large environment extra arguments are causing this.
|
I think these issues are related: #1798 |
See comment: #1798 (comment) |
|
Works now, thank you |
Issue is reproduced in version
|
@HazAT I've checked, the latest workable version is |
@feorex Angular attaches debug context in their development environment which is enormous object. We found the issue and patched it. Release is processing now. Will ping you (few minutes) once it's up. |
@feorex could you please give a |
@kamilogorek Just tried |
Hi,
Following the fix of #1707, the issue (or an other one) is still active: there is an infinite loop somewhere that can be created in some situation.
I don't know how to reproduce and it but I know that addbreadcrumb is responsible for this infinite loop.
cf. https://ibb.co/KXcprWY to have more information, the function "standardizer" is called without ending.
It seems to be even worst than the previous version because I used this workaround to prevent browser crashing: initSentry({
dsn: #####,
beforeBreadcrumb(breadcrumb, hint) {
if(get( breadcrumb , "error.data.extra.arguments")) {
breadcrumb.error.data.extra.arguments = [];
}
return breadcrumb;
}
});
This workaround doesn"t work anymore, so I have to get back to the previous version. The problem is that with this workaround It seems impossible to have information about where errors happens in the code (line number etc).
Dorian
The text was updated successfully, but these errors were encountered: