UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:
1. Use the Remote Debugging Protocol on headless and enable network request interception (continue all requests without modifying them, i.e. client.send('Network.continueInterceptedRequest',{interceptionId: params.interceptionId}) )
2. Navigate to https://www.merdeka.com/peristiwa/habib-rizieq-tegur-keras-presidium-alumni-212-karena-bela-hary-tanoe.html

What is the expected behavior?
Chrome should intercept requests and allow them to continue without throwing errors. 

What went wrong?
One request on that page causes Chrome to throw an "Invalid InterceptionId" error (https://chromium.googlesource.com/chromium/src.git/+/refs/heads/lkcr/content/browser/devtools/devtools_url_request_interceptor.cc#121), even though all interceptionId's are directly passed to the continueInterceptedRequest event.

Node returns this error as:
(node:7600) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Invalid InterceptionId.
(node:7600) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Even when interceptions are always continued, this error seems to appear on a wide variety of unrelated webpages.  

When several pages which cause this error are loaded in close succession (>100 errors), Chrome usually crashes. This is the behaviour on both 63.0.3213.3 and 62.0.3202.18

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 63.0.3213.3  Channel: dev
OS Version: 17.04
Flash Version: 

I'm using the NodeJS library chrome-remote-interface to open/manage the connection with CDP