Repository navigation
funky behavior inside Proxy handler function #6464
Description
- Version: 6.0.0
- Platform: darwin
- Subsystem: 10.11

Activity
- addedconfirmed-bugIssues and PRs for confirmed bugs.Issues and PRs for confirmed bugs.utilIssues and PRs related to the built-in util module.Issues and PRs related to the built-in util module.
on Apr 29, 2016 Confirmed, it seems that util.inspect doesn't know what to make of Proxy objects in certain cases... will look into it.
The issue here is that the
firstthird argument passed togetis the proxy object itself. This is passed toconsole.log()which does autil.inspect(). Now,util.inspect()attempts to walk the properties for the Proxy object, which ends up recursively callingget... which leads to the max call stack error.👍
Any ideas about
arguments[2]in the last screenshot?Yes, I just realized in my comment above I mentioned the wrong argument... the third argument passed to
getis the proxy object. Look here .. the get argument is passed three arguments, the target, the property name and the proxy.Is it recursive because the object itself is the argument? , is this a loop structure? I mean is the arrow function recursive.
- added a commit that references this issue
on May 4, 2016 - added a commit that references this issue
on May 4, 2016 - added a commit that references this issue
on Jul 27, 2026

