Clever Geek Handbook

New Function (...) returns undefined in Chrome 58 in debug mode

I ran into some strange behavior new Function(...)

in Chrome 58. When executed new Function(...)

in the developer console when paused at the debug point, it returns instead of the generated function undefined

.

Jsbin example: http://jsbin.com/raluwu/edit?html,output

<!DOCTYPE html>
<html>
<body>
  <script>
    // open the developer console in Chrome 58, 
    // and run this code until the debug point
    debugger;
    //eval('debugger');
    // when at the debug point, enter the following in the console:
    //
    //     var f = new Function ('a', 'return a + a');
    //     // f should be a function but is undefined when in debug mode
    // 
    //     console.log(f(2));   
    //     // should return 4, but throws "Uncaught TypeError: f is not a function"

    // without debug point, everything runs fine:
    var f = new Function ('a', 'return a + a');
    console.log(f(2)); // 4
  </script>
</body>
</html>

Is this a bug in Chrome?

+3


source to share


1 answer


I did some more digging and found a bug report for this issue:

https://bugs.chromium.org/p/chromium/issues/detail?id=705149



So this is indeed a bug in Chrome

+2


source






More articles:


All Articles