{"action":"created","issue":{"url":"https://api.github.com/repos/ChromeDevTools/debugger-protocol-viewer/issues/88","repository_url":"https://api.github.com/repos/ChromeDevTools/debugger-protocol-viewer","labels_url":"https://api.github.com/repos/ChromeDevTools/debugger-protocol-viewer/issues/88/labels{/name}","comments_url":"https://api.github.com/repos/ChromeDevTools/debugger-protocol-viewer/issues/88/comments","events_url":"https://api.github.com/repos/ChromeDevTools/debugger-protocol-viewer/issues/88/events","html_url":"https://github.com/ChromeDevTools/debugger-protocol-viewer/issues/88","id":268094409,"number":88,"title":"Protocol errors when connecting on Debian via Puppeteer","user":{"login":"chrbala","id":6834804,"avatar_url":"https://avatars0.githubusercontent.com/u/6834804?v=4","gravatar_id":"","url":"https://api.github.com/users/chrbala","html_url":"https://github.com/chrbala","followers_url":"https://api.github.com/users/chrbala/followers","following_url":"https://api.github.com/users/chrbala/following{/other_user}","gists_url":"https://api.github.com/users/chrbala/gists{/gist_id}","starred_url":"https://api.github.com/users/chrbala/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chrbala/subscriptions","organizations_url":"https://api.github.com/users/chrbala/orgs","repos_url":"https://api.github.com/users/chrbala/repos","events_url":"https://api.github.com/users/chrbala/events{/privacy}","received_events_url":"https://api.github.com/users/chrbala/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-24T16:11:22Z","updated_at":"2017-10-25T19:32:18Z","closed_at":"2017-10-25T19:32:18Z","author_association":"NONE","body":"I'm not exactly sure that this is a debugger-protocol-viewer error, but I thought I'd start here because I'm getting protocol errors.\r\n\r\n### What steps will reproduce the problem?\r\n\r\n1. Start up a Chrome headless instance without seccomp (see below for Docker images)\r\n2. Get websocket link with the /json endpoint.\r\n3. Connect to Chrome instance in Node via Puppeteer@0.12.0\r\n\r\n### What is the expected result?\r\n\r\nThe connection is successfully made.\r\n\r\n### What happens instead of that?\r\n\r\nWhen using [justinribeiro/chrome-headless](https://hub.docker.com/r/justinribeiro/chrome-headless/), I get the following error:\r\n```\r\nProtocol error (Performance.enable): 'Performance.enable' wasn't found undefined\r\n      \r\n      at Session._onMessage (../../node_modules/puppeteer/node6/Connection.js:272:25)\r\n      at Connection.<anonymous> (../../node_modules/puppeteer/node6/Connection.js:150:19)\r\n      at next (native)\r\n      at step (../../node_modules/puppeteer/node6/Connection.js:113:24)\r\n      at Promise (../../node_modules/puppeteer/node6/Connection.js:131:12)\r\n      at fn (../../node_modules/puppeteer/node6/Connection.js:109:10)\r\n      at Connection._onMessage (../../node_modules/puppeteer/node6/Connection.js:133:3)\r\n      at emitOne (events.js:96:13)\r\n      at WebSocket.emit (events.js:188:7)\r\n      at Receiver._receiver.onmessage (../../node_modules/ws/lib/WebSocket.js:143:47)\r\n      at Receiver.dataMessage (../../node_modules/ws/lib/Receiver.js:389:14)\r\n      at Receiver.getData (../../node_modules/ws/lib/Receiver.js:330:12)\r\n      at Receiver.startLoop (../../node_modules/ws/lib/Receiver.js:165:16)\r\n      at Receiver.add (../../node_modules/ws/lib/Receiver.js:139:10)\r\n      at Socket._ultron.on (../../node_modules/ws/lib/WebSocket.js:139:22)\r\n      at emitOne (events.js:96:13)\r\n      at Socket.emit (events.js:188:7)\r\n      at readableAddChunk (_stream_readable.js:176:18)\r\n      at Socket.Readable.push (_stream_readable.js:134:10)\r\n      at TCP.onread (net.js:547:20)\r\n```\r\n\r\nI thought it might be from the month-old Chrome version in the build, so I tried again with my own fresh container, [chrbala/headless-chrome](https://hub.docker.com/r/chrbala/headless-chrome/) which uses the same dockerfile and was built with Chromium 62.0.3202.62-1. The version of Puppeteer I'm using declares that it's compatible with chromium_revision of 508693, but I'm not sure how that maps to the semantic Chromium versions.\r\n\r\nMy build had a different error:\r\n```\r\nProtocol error (Runtime.callFunctionOn): Invalid parameters objectId: string value expected\r\n      \r\n      at Session._onMessage (../../node_modules/puppeteer/node6/Connection.js:272:25)\r\n      at Connection.<anonymous> (../../node_modules/puppeteer/node6/Connection.js:150:19)\r\n      at next (native)\r\n      at step (../../node_modules/puppeteer/node6/Connection.js:113:24)\r\n      at Promise (../../node_modules/puppeteer/node6/Connection.js:131:12)\r\n      at fn (../../node_modules/puppeteer/node6/Connection.js:109:10)\r\n      at Connection._onMessage (../../node_modules/puppeteer/node6/Connection.js:133:3)\r\n      at emitOne (events.js:96:13)\r\n      at WebSocket.emit (events.js:188:7)\r\n      at Receiver._receiver.onmessage (../../node_modules/ws/lib/WebSocket.js:143:47)\r\n      at Receiver.dataMessage (../../node_modules/ws/lib/Receiver.js:389:14)\r\n      at Receiver.getData (../../node_modules/ws/lib/Receiver.js:330:12)\r\n      at Receiver.startLoop (../../node_modules/ws/lib/Receiver.js:165:16)\r\n      at Receiver.add (../../node_modules/ws/lib/Receiver.js:139:10)\r\n      at Socket._ultron.on (../../node_modules/ws/lib/WebSocket.js:139:22)\r\n      at emitOne (events.js:96:13)\r\n      at Socket.emit (events.js:188:7)\r\n      at readableAddChunk (_stream_readable.js:176:18)\r\n      at Socket.Readable.push (_stream_readable.js:134:10)\r\n      at TCP.onread (net.js:547:20)\r\n```\r\n\r\nBoth of the above Docker images were built with [this docker file](https://hub.docker.com/r/justinribeiro/chrome-headless/~/dockerfile/)."},"comment":{"url":"https://api.github.com/repos/ChromeDevTools/debugger-protocol-viewer/issues/comments/339445051","html_url":"https://github.com/ChromeDevTools/debugger-protocol-viewer/issues/88#issuecomment-339445051","issue_url":"https://api.github.com/repos/ChromeDevTools/debugger-protocol-viewer/issues/88","id":339445051,"user":{"login":"paulirish","id":39191,"avatar_url":"https://avatars0.githubusercontent.com/u/39191?v=4","gravatar_id":"","url":"https://api.github.com/users/paulirish","html_url":"https://github.com/paulirish","followers_url":"https://api.github.com/users/paulirish/followers","following_url":"https://api.github.com/users/paulirish/following{/other_user}","gists_url":"https://api.github.com/users/paulirish/gists{/gist_id}","starred_url":"https://api.github.com/users/paulirish/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/paulirish/subscriptions","organizations_url":"https://api.github.com/users/paulirish/orgs","repos_url":"https://api.github.com/users/paulirish/repos","events_url":"https://api.github.com/users/paulirish/events{/privacy}","received_events_url":"https://api.github.com/users/paulirish/received_events","type":"User","site_admin":false},"created_at":"2017-10-25T19:32:18Z","updated_at":"2017-10-25T19:32:18Z","author_association":"OWNER","body":"the `Performance` domain was added on 2017-08-10 so whatever Chromium is in that docker build is older than that.\r\n\r\nPptr doesn't run against any version of chrome, so that's the problem. you'll need to get the chromium version updated to 63.\r\n\r\nsee the NOTE here: https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#puppeteerlaunchoptions"}}
{"actor":{"display_login":"paulirish"}}