-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
@sentry/angular cause infinite re-render loop #2974
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
Comments
This is currently a known issue, the workaround is to disable console breadcrumbs to prevent the loop:
|
The above comment doesn't seem to help me. Getting an infinite loop of logs using the Sentry error handler: {
provide: ErrorHandler,
useValue: Sentry.createErrorHandler({ showDialog: false }),
}, This doesn't happen if I create a custom handler that re-throws the error like so: import { ErrorHandler, Injectable } from '@angular/core';
import * as Sentry from '@sentry/browser';
@Injectable()
export class SentryErrorHandler implements ErrorHandler {
handleError(error: Error & { originalError?: Error }) {
Sentry.captureException(error.originalError || error);
console.error(error);
if (error instanceof TypeError) {
throw error;
}
}
} Error:
Edit: You can disregard my message about infinite looping as it was related to my app and not caused by Sentry |
@intellix I wasn't able to reproduce the issue locally. Can you provide some kind of repro case? |
Closing the issue as a part of large repository cleanup, due to it being inactive and/or outdated. |
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
Description
When initializing Sentry library Angular app won't stop to re-render.
The Sentry intializer starts an infinite re-render loop that start consuming a lot of CPU and if there any sort of console.log or something like that in each interaction could eventually kill the browser.
This can be reproducible in a brand new angular-cli app
The text was updated successfully, but these errors were encountered: