Closed mortargrind closed 2 years ago
I'm experiencing the same issue on Nuxt / VueJS app :
Some - not all - errors lead to an infinite loop.
For instance, here's an error that would create this infinite loop (Sentry disabled, vue-router@3.3.1):
vue-router.esm.js:2060 Uncaught (in promise) Error: Navigation cancelled from "/fr/p/465/offer/establishment" to "/fr/p/465/offer/establishment/general" with a new navigation.
at iterator (vue-router.esm.js:2212)
at step (vue-router.esm.js:1896)
at vue-router.esm.js:1897
at vue-router.esm.js:2237
at Vue._callee3$ (client.js:171)
at tryCatch (runtime.js:45)
at Generator.invoke [as _invoke] (runtime.js:274)
at Generator.prototype.<computed> [as next] (runtime.js:97)
But when I enable Sentry:
Many folks experienced the same in https://github.com/vuejs/vue-devtools/issues/460
(seems unrelated to vue-devtools
but still, this issue helped me workaround it by disabling Sentry.)
The same is happening for me with @nuxtjs/sentry@4.0.3
and appears to be after vue-router
updated from 3.2.0
to 3.3.4
. Downgrading to 3.2.0
fixed the issue.
From all my research online, others with the same issue seemed to get it whenever they either:
vue-router@3.3.0
introduced some changes to how errors are handled, so perhaps that is what caused the issue. After downgrading I'm able to see what exception I was receiving as well; it seemed to be suppressed before.
I can confirm what @robere2 states.
I am using the following:
@nuxtjs@2.13.3
which depends on vue-router@3.3.4
@nuxtjs/sentry@4.13
For me, I encountered this error from the following error thrown in vue-router
:
Uncaught (in promise) Error: Redirected when going from "/foo" to "/bar" via a navigation guard
The above error was triggered by going from /foo
to /bar
, which has a navigation guard causing a redirect to /baz
, which is a non-breaking error. However, Sentry caused the browser to freeze because in recursion.
Closing this issue as Vue specific issues are being tracked in #2957. If you are still encountering issues with @sentry/browser
, please re-open and let us know. Thanks!
I'm sitting in the same boat as @superbiche @robere2 and @ERPedersen using Nuxt.js and Vue Router and when getting a Redirect Error like the one @ERPedersen posted above, Sentry crashes my App.
Since I am using nuxt@2.15
I am not able to downgrade vue-router to a working level anymore because it won't be compatible with my (required) Nuxt Version anymore.
The ticket you linked @AbhiPrasad is related to something else as far as I can tell. Therefore I'd appreciate reopening it. Let me know in case I can help further narrowing down the issue.
Will re-open, a reproduction or something similar will help us debug, otherwise a link to your Sentry error also would help out!
@floriankapaun Could you create a repro? Our app evolved a lot since then, we added so many workarounds to avoid this issue that I can't even reproduce it :sweat:
Thanks @AbhiPrasad!
Hey @superbiche I set something up for you. Have a look at my Repository. Let me know if you have further questions. 🙂
At least in the case of using Nuxt with the @nuxtjs/sentry
module, I believe that the freeze you are seeing is due to this Sentry SDK issue: https://github.com/getsentry/sentry-javascript/issues/4186
I have made a workaround for that in https://github.com/nuxt-community/sentry-module/releases/tag/v5.1.7 . Feel free to try it out.
(I'm also fixing it in the Sentry SDK itself but with the workaround in the Nuxt module it should work already)
The fix is released with SDK version 6.17.4
: https://github.com/getsentry/sentry-javascript/releases/tag/6.17.4. If this still occurs, please let us know!
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
Description
Hello.
We are getting a
RangeError: Maximum call stack size exceeded
error approximately once a month in our application.When I check the breadcrumbs what I see is this:
The error report link is here https://sentry.io/share/issue/1ce9d6729fee41909ee71e2c871f07e5/.
Since there is no breadcrumb or stacktrace that is related to our app, I am suspecting that this is related to Sentry itself. I am planning on disabling the DOM breadcrumb integration for now so even if it's related to our app, Sentry related stuff won't be appearing in the report.
If you have any idea that can confirm or reject my suspicions I am all ears. I can also share the details of our tech stack and the way we use the SDK if that can help you.
Thanks.