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

vue3 render warning loop #5916

Closed
3 tasks done
Rockergmail opened this issue Oct 8, 2022 · 1 comment · Fixed by #6014
Closed
3 tasks done

vue3 render warning loop #5916

Rockergmail opened this issue Oct 8, 2022 · 1 comment · Fixed by #6014
Labels

Comments

@Rockergmail
Copy link
Contributor

Is there an existing issue for this?

How do you use Sentry?

Self-hosted/on-premise

Which package are you using?

@sentry/vue

SDK Version

7.12.1

Framework Version

Vue 3.2.23

Link to Sentry event

No response

Steps to Reproduce

  1. add a route to a new page
  2. the new page's template add one undeclared var
  3. visit the new page. and the warning message from instruments.js will go on and on until the page dead.

The reason I found is that, when rendering gets a warning, will call console.warn to console the error stack. But the stack includes a Proxy variable. When sentry do safeJoin with String(value), will visit the proxy variable, and visit the get handler, got undefined, so vue will call console.warn again. So the warning loop happends.

image

`checkStored` is my undeclared var

image

image

image

image


I tried to fix but I can not deal with how to test a var is Proxied. The way I test will trigger the get handler, so I just disable the console option of Breadcrumbs to solve the problem temporary.
Even though I should clean my code without undeclared var, I think it is still a bug.

Expected Result

do not loop warning

Actual Result

do loop waning.

@AbhiPrasad
Copy link
Member

Hey, thanks for writing in. Backlogging, but PRs are welcome for those who would like to help debug and fix this!

Related issues:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants