-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: Recursive logging bug with console recording #1136
fix: Recursive logging bug with console recording #1136
Conversation
🦋 Changeset detectedLatest commit: cdec9e6 The changes in this PR will be included in the next version bump. This PR includes changesets to release 7 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This a very interesting edge case. Thanks for your great description and fix.
Could you please help us add the change log? Seems like I don't have permission to add it to your branch. |
Happily! (How do I do that? 😅 ) Perhaps something to add to the PR template? |
@YunFeng0817 I think I did it? (I just clicked the link in the bots comment but please double check I got that right 🙈 ) |
@benjackwhite Yes, you did. I will merge it once CI passes. |
Originally reported here
Problem
Thanks to some debugging with a customer, we found an interesting "edge" case that can trigger an infinite loop via console logs. The context is this was a Vue.js app that was logging some warnings which contained objects within that warning with Proxied methods that triggered logs themselves.
The situation is like this (WARNING: If you run this with console log recording enabled your browser will freeze).
proxy
objectget
call which itself is logging a warningSolution