Apparently, Chrome debugger internally calls Object.getOwnPropertyNames() for objects, some of which lack a toString() method. This causes the debugger to fail, not being able to show the value of the variables in the current frame.
Every time a key is pressed in the console while in the debugger, an exception is shown because of this too.
This commit adds an additional check to solve this annoying problem.
archangel-irk
commented
8 years ago
Apparently, Chrome debugger internally calls
Object.getOwnPropertyNames()for objects, some of which lack atoString()method. This causes the debugger to fail, not being able to show the value of the variables in the current frame.Every time a key is pressed in the console while in the debugger, an exception is shown because of this too.
This commit adds an additional check to solve this annoying problem.