UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.162 Safari/537.36

Steps to reproduce the problem:
1. i run gulp with node8.7(the newest 9.8 is also not work,the proble is not node ,is devtool)
2. node --inspect=9222 --inspect-brk node_modules/gulp/bin/gulp.js --gulpfile  mygulpfile.js
the mygulpfile.js's gulp task is aways run,not exit,just like this:
require("gulp").task("default", function (callback) { 
   console.log('gulp task');
   //callback();  //don't call callback ,and it can hold the task not finish,so it aways run not exit,this use is common,not problem.
});
3. open devtool, it auto goto debug model,and stoped at node_modules/gulp/bin/gulp.js's first line ,no problem.
4.when resume , the js run with any error ,and just as expect, it is hold,not exit.
5.but when I open the mygulpfile.js file, the devtool report websockt conection closed, and reconect is not work, this can reproduct every time. I add debugger instruction into fist line of mygulpfile.js , re run gulp task, re open devtool, but when run to debugger line, with the mygulpfile.js file auto opend , the websocket connection also closed. mygulpfile.js's content is short, it's a smarl file , and code is no error no warning.
6.I work with the gulpfile two years, just in recent days ,chrome update to 65version,this happened, I try get 63version , it work right no this problem. and I use 64 version before update, and also work right. So i think the problem is 65version.

What is the expected behavior?

What went wrong?
I work with the gulpfile two years, just in recent days ,chrome update to 65version,this happened, I try get 63version , it work right no this problem. and I use 64 version before update, and also work right. So i think the problem is 65version.

Did this work before? N/A 

Chrome version: 65.0.3325.162  Channel: stable
OS Version: OS X 10.12.6
Flash Version: