Unable to reproduce the issue on reported chrome version 63.0.3239.108 and on the latest canary 65.0.3310.0 using Mac 10.13.1 with the below mentioned steps.
1. Launched chrome and opened dev tools
2. Navigated to Sources>Snippets>New snippet
3. Created the snippet using the file attached in comment#0
4. Placed a break point in the function.
5. Used console to look arguments

We observed the "Uncaught ReferenceError: arguments is not defined" is seen and it is not parsing the arguments. Attaching the screen cast of the same.

@Reporter: Could you please have a look at the screen cast and let us know if we have missed any steps in reproducing the issue. Any further inputs from your end helps us to triage the issue in a better way.

Thanks!

Deleted: 798469.mp4 929 KB

	798469.mp4 929 KB View Download

you forgot to run the script and try this when the debugger stops on that breakpoint.
press that little play button on your bottom left side of the source code

Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Able to reproduce the issue on reported chrome version 63.0.3239.108 and on the latest canary 65.0.3310.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.1. As the issue is seen from M50(50.0.2661.0) considering it as non-regression and marking it as Untriaged. Attaching the screencast of 50.02661.0 and screenshot of 65.0.3310.0 for reference.

Thanks!

Deleted: 798469 M50.mp4 5.0 MB

	798469 M50.mp4 5.0 MB View Download

Deleted: 798469 M65.png 1.1 MB

	798469 M65.png 1.1 MB View Download

I believe that it is feature and not a bug actually which allows you to easily inspect arguments which were passed to arrow function. I personally use it a lot.
How critical this issue to you?

since in runtime “arguments” aren’t available by definition, devtool can mislead devs to use arguments in their code. In my opinion, devtool should emulate actual runtime environment, thus the behavior is not aligned and should be regarded as bug.

A guy who uses Arrow function for the first time, it'll be confused while debugging code shown below:


(function () {

    var test = () => {

        debugger;

        console.log( arguments );    // Mouse cursor hovers at this `arguments`, DevTools will show `['b', 'c']`
    };

    test.call(null, 'b', 'c');

})('a');

It is fixed in current Google Chrome Stable and in latest ToT Chromium.