itsgoingd@ - Thanks for filing the issue...!!

Could you please provide a sample extension file/test file to test the issue from TE-end.
this will help us in triaging the issue further.

Thanks...!! 

I'm seeing this as well when I try to use the network.getHar() function or the network.onRequestFinished.addListener() function. Unfortunately it's breaking my company's ad debugging plugin. It seems the NetworkLog.HARLog.pseudoWallTime() is returning a date String rather than a Date. Then the expiresDate function in SDK.Cookie calls getTime() on that string and throws an error.

Deleted: Screen Shot 2018-03-19 at 1.21.21 PM.png 227 KB

	Screen Shot 2018-03-19 at 1.21.21 PM.png 227 KB View Download

I met same issue.
Chrome version: 65.0.3325.162 (Official Build). Channel: stable
OS: Windows 10 build 1709

It occures when Set-Cookie response header has max-age (RFC 6265).
If the header has expires instead of max-age, no errors happen.
IMO, first report is correct.

I created a minimal reproduce code.

1. install this extension: https://gist.github.com/Tietew/b77778b67af8e66299a62a40b78e8598
2. open blank tab
3. open devtool
4. open devtool's devtool
5. navigate to: https://9rr7ehinag.execute-api.ap-northeast-1.amazonaws.com/test/chromium801306
6. console of devtool's devtool (4) shows following error

TypeError: targetDate.getTime is not a function TypeError: targetDate.getTime is not a function
    at SDK.Cookie.expiresDate (inspector.js:3603)
    at NetworkLog.HAREntry._buildCookie (inspector.js:6023)
    at Array.map (<anonymous>)
    at NetworkLog.HAREntry._buildCookies (inspector.js:6022)
    at NetworkLog.HAREntry._buildResponse (inspector.js:6009)
    at NetworkLog.HAREntry.build (inspector.js:6003)
    at Extensions.ExtensionServer._notifyRequestFinished (inspector.js:7414)
    at SDK.NetworkManager.dispatchEventToListeners (inspector.js:482)
    at SDK.NetworkDispatcher._finishNetworkRequest (inspector.js:5671)
    at SDK.NetworkDispatcher.loadingFinished (inspector.js:5644)

This issue has been fixed by https://bugs.chromium.org/p/chromium/issues/detail?id=817970
Right?

I confirmed the same bug with version: 65.0.3325.181.
When is the corrected?

I have written a chrome extension. This extension uses
devTools.network.onRequestFinished.addListener(function(request) {...}

Flow was working as expected and request were captured by listener appropriately till version 64.x

Unfortunately, with the newer version of Google Chrome - Version 65.0.3325.181 (Official Build) (64-bit), this functionality seems to be broken.

Now, I am getting javascript errors. Please refer to the attached text file for reference.

Will be great if someone can please take a look and provide your comments.

Thanks for all your help in advance.

Deleted: error.txt 34.2 KB

error.txt 34.2 KB View Download

I've updated my extension to use the `webRequest` api instead since reporting this issue, as it wasn't going to be fixed before a stable channel release.

It's pretty straight-forward and also supported in Firefox, example implementation - https://github.com/itsgoingd/clockwork-chrome/blob/master/Clockwork%20Chrome/assets/javascripts/chrome/background.js#L44-L59, https://github.com/itsgoingd/clockwork-chrome/blob/master/Clockwork%20Chrome/assets/javascripts/extension.js#L49-L80