New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 667699 link

Starred by 3 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome is sending a wrong formatted number

Reported by daniele....@gmail.com, Nov 22 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14

Steps to reproduce the problem:
1. OSX with Chrome 54, open Chrome in debugging mode:
    /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --remote-debugging-port=9222

2. Now try to open the FRAME to sniff the protocol, as described here:
https://developer.chrome.com/devtools/docs/debugger-protocol#remote

3. Watch in the console:
[2883:775:1122/101132:ERROR:CONSOLE(1557)] "SyntaxError: Unexpected number in JSON at position 94 SyntaxError: Unexpected number in JSON at position 94
    at JSON.parse (<anonymous>)
    at WebInspector.MainConnection.dispatch (chrome-devtools://devtools/bundled/inspector.js:4413:154)
    at WebInspector.MainConnection._dispatchMessage (chrome-devtools://devtools/bundled/inspector.js:10591:7)
    at WebInspector.Object.dispatchEventToListeners (chrome-devtools://devtools/bundled/inspector.js:738:185)
    at innerDispatch (chrome-devtools://devtools/bundled/inspector.js:1557:58)
    at InspectorFrontendAPIImpl._dispatch (chrome-devtools://devtools/bundled/inspector.js:1556:1)
    at DevToolsAPIImpl._dispatchOnInspectorFrontendAPI (<anonymous>:62:21)
    at DevToolsAPIImpl.dispatchMessage (<anonymous>:147:14)
    at <anonymous>:1:13", source: chrome-devtools://devtools/bundled/inspector.js (1557)

What is the expected behavior?
I should get a JSON correctly formatted, but isn't.

What went wrong?
Take a look to this jSON, you can clearly see that "wallTime" and "timestamp" are bad formatted.

{"method":"Network.requestWillBeSent","params":{"requestId":"87916.125","frameId":"87916.2","loaderId":"87916.2","documentURL":"https://github.com/","request":{"url":"https://github.com/","method":"GET","headers":{"Upgrade-Insecure-Requests":"1","User-Agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.98 Safari/537.36"},"mixedContentType":"none","initialPriority":"VeryHigh"},"timestamp":397570,616493,"wallTime":1479730888,909882,"initiator":{"type":"other"},"type":"Document"}}

Did this work before? N/A 

Chrome version: Versione 54.0.2840.98 (64-bit)  Channel: stable
OS Version: OS X 10.12.1
Flash Version: 

Can God help you guys.
 
Labels: M-54 Needs-Triage-M54
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
This looks very similar to https://bugs.chromium.org/p/v8/issues/detail?id=5551. Can you reproduce this on Chrome Canary?
Status: Fixed (was: Assigned)
I was able to reproduce this problem in M54 and wasn't able to reproduce it in Canary.

Sign in to add a comment