-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Crash when calling console.dir on a revoked Proxy #43095
Comments
daeyeon
added a commit
to daeyeon/node
that referenced
this issue
May 14, 2022
Fixes: nodejs#43095 Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com
daeyeon
added a commit
to daeyeon/node
that referenced
this issue
May 14, 2022
Fixes: nodejs#43095 Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com
daeyeon
added a commit
to daeyeon/node
that referenced
this issue
May 14, 2022
Fixes: nodejs#43095 Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com
daeyeon
added a commit
to daeyeon/node
that referenced
this issue
May 14, 2022
Fixes: nodejs#43095 Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com
daeyeon
added a commit
to daeyeon/node
that referenced
this issue
May 14, 2022
Fixes: nodejs#43095 Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com
daeyeon
added a commit
to daeyeon/node
that referenced
this issue
May 14, 2022
Fixes: nodejs#43095 Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com
guangwong
pushed a commit
to noslate-project/node
that referenced
this issue
Oct 10, 2022
Fixes: nodejs/node#43095 Signed-off-by: Daeyeon Jeong daeyeon.dev@gmail.com PR-URL: nodejs/node#43100 Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v18.1.0 (Windows), v16.15.0 (WSL1), v16.14.2 (WSL1), v16.14.0 (Windows), v12.16.1 (repl.it)
Platform
Microsoft Windows NT 10.0.19044.0 x64
Subsystem
console
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
v16.15.0 on WSL1:
v18.1.0 on Windows:
Additional information
util.inspect(r.proxy)
(orconsole.log(r.proxy)
) doesn't crash but it does throw an exception:If you call
util.inspect(r)
(orconsole.log(r)
) instead (i.e. on the wrapper object) the error is slightly different (presumably because it's wrapped in an assertion):No problems in a Chrome devtools console.
The text was updated successfully, but these errors were encountered: