{"action":"created","issue":{"url":"https://api.github.com/repos/sitespeedio/sitespeed.io/issues/596","labels_url":"https://api.github.com/repos/sitespeedio/sitespeed.io/issues/596/labels{/name}","comments_url":"https://api.github.com/repos/sitespeedio/sitespeed.io/issues/596/comments","events_url":"https://api.github.com/repos/sitespeedio/sitespeed.io/issues/596/events","html_url":"https://github.com/sitespeedio/sitespeed.io/issues/596","id":58802911,"number":596,"title":"browsermobproxy fails with error: TypeError: Cannot read property 'repeatView' of undefined","user":{"login":"Vandrix","id":11033723,"avatar_url":"https://avatars.githubusercontent.com/u/11033723?v=3","gravatar_id":"","url":"https://api.github.com/users/Vandrix","html_url":"https://github.com/Vandrix","followers_url":"https://api.github.com/users/Vandrix/followers","following_url":"https://api.github.com/users/Vandrix/following{/other_user}","gists_url":"https://api.github.com/users/Vandrix/gists{/gist_id}","starred_url":"https://api.github.com/users/Vandrix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Vandrix/subscriptions","organizations_url":"https://api.github.com/users/Vandrix/orgs","repos_url":"https://api.github.com/users/Vandrix/repos","events_url":"https://api.github.com/users/Vandrix/events{/privacy}","received_events_url":"https://api.github.com/users/Vandrix/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-02-24T20:52:17Z","updated_at":"2015-02-25T20:33:36Z","closed_at":null,"body":"I'm running into browsermobproxy errors lately.\r\n\r\nI run with: \r\nxvfb-run --server-args=\"-screen 0 1920x1080x24\" sitespeed.io -f filename -r domain -b chrome --viewPort 1920x1080 --screenshot --gpsiKey key --wptConfig jsonfile --wptHost private instance --wptKey apikey\r\n\r\nbrowsermobproxy.log:\r\n\r\n2015-02-24T20:00:03.942Z - info: [browsermobproxy] stdout:Unable to find conf/bmp-logging.properties. Using default logging configuration.\r\n2015-02-24T20:00:03.944Z - info: [browsermobproxy] stdout:\r\n2015-02-24T20:00:04.784Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:04 n.l.b.p.Main         - Starting BrowserMob Proxy version 2.0.0\r\n2015-02-24T20:00:04.853Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:04 o.e.j.u.log          - jetty-2.0.0\r\n2015-02-24T20:00:04.916Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:04 o.e.j.u.log          - started o.e.j.s.ServletContextHandler{/,null}\r\n2015-02-24T20:00:06.392Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:06 o.e.j.u.log          - Started SelectChannelConnector@0.0.0.0:9092\r\n2015-02-24T20:00:21.792Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:21 n.l.b.p.j.h.HttpSer~ - Version Jetty/2.0.0\r\n2015-02-24T20:00:21.795Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:21 n.l.b.p.j.u.Contain~ - Started HttpContext[/,/]\r\n2015-02-24T20:00:21.805Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:21 n.l.b.p.j.h.SocketL~ - Started SocketListener on 0.0.0.0:9091\r\n2015-02-24T20:00:21.806Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:21 n.l.b.p.j.u.Contain~ - Started net.lightbody.bmp.proxy.jetty.jetty.`Server@347fd24a`\r\n2015-02-24T20:00:42.459Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:42 n.l.b.p.j.u.Threade~ - Stopping Acceptor ServerSocket[addr=/0.0.0.0,localport=9091]\r\n2015-02-24T20:00:42.560Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:42 n.l.b.p.j.h.SocketL~ - Stopped SocketListener on 0.0.0.0:9091\r\n2015-02-24T20:00:42.695Z - error: [browsermobproxy] stderr:INFO 02/24 20:00:42 n.l.b.p.j.u.Contain~ - Stopped HttpContext[/,/]\r\nINFO 02/24 20:00:42 n.l.b.p.j.u.Contain~ - Stopped net.lightbody.bmp.proxy.jetty.jetty.`Server@347fd24a`\r\n\r\n2015-02-24T20:11:59.598Z - error: [browsermobproxy] TypeError: Cannot read property 'repeatView' of undefined\r\n    at /usr/local/lib/node_modules/sitespeed.io/lib/collectors/pages.js:174:48\r\n    at Array.forEach (native)\r\n    at collectWPT (/usr/local/lib/node_modules/sitespeed.io/lib/collectors/pages.js:161:28)\r\n    at Object.exports.processPage (/usr/local/lib/node_modules/sitespeed.io/lib/collectors/pages.js:34:5)\r\n    at /usr/local/lib/node_modules/sitespeed.io/lib/collector.js:126:7\r\n    at Array.forEach (native)\r\n    at Collector.collectPageData (/usr/local/lib/node_modules/sitespeed.io/lib/collector.js:125:19)\r\n    at processAnalysisResults (/usr/local/lib/node_modules/sitespeed.io/lib/analyze/analyzer.js:134:17)\r\n    at /usr/local/lib/node_modules/sitespeed.io/lib/analyze/analyzer.js:69:17\r\n    at /usr/local/lib/node_modules/sitespeed.io/node_modules/async/lib/async.js:254:17\r\n\r\nsitespeed.io.log:\r\n\r\n2015-02-24T20:00:03.542Z - info: [sitespeed] OS: 'linux 3.13.0-43-generic', Node.js: 'v0.12.0', sitespeed: '3.1.2', phantomJs: '1.9.8', java: '1.7.0_75', browsertime: '0.8.21'\r\n2015-02-24T20:00:03.544Z - info: [sitespeed] Analyze 4 sites\r\n2015-02-24T20:00:03.668Z - info: [sitespeed] Will analyze 1 pages\r\n2015-02-24T20:00:06.396Z - info: [sitespeed] Running YSlow for http://private.tld [phantomjs]\r\n2015-02-24T20:00:13.191Z - info: [sitespeed] Running Google Page Speed Insights for http://private.tld\r\n2015-02-24T20:00:20.492Z - info: [sitespeed] Queueing browsertime for http://private.tld chrome\r\n2015-02-24T20:00:20.494Z - info: [sitespeed] Running browsertime for chrome http://private.tld\r\n2015-02-24T20:00:42.725Z - info: [sitespeed] Running WebPageTest http://private.tld  pollResults=10, timeout=3600, firstViewOnly=false, runs=3, private=true, aftRenderingTime=true, location=Local-WPTDriver:Chrome, connectivity=Cable, video=true, server=private\r\n2015-02-24T20:11:55.218Z - info: [sitespeed] Taking screenshot for http://private.tld\r\n2015-02-24T20:11:59.551Z - error: [sitespeed] Could not fetch data for aggregator: TTFBWPT: err: [TypeError: Cannot read property 'forEach' of undefined]\r\n\r\n\r\njava -version \r\njava version \"1.7.0_75\"\r\nOpenJDK Runtime Environment (IcedTea 2.5.4) (7u75-2.5.4-1~trusty1)\r\nOpenJDK 64-Bit Server VM (build 24.75-b04, mixed mode)\r\n`\r\nJSON file:\r\n\r\n{\r\n  \"server\": \"private\",\r\n  \"location\": \"Local-WPTDriver:Chrome\",\r\n  \"connectivity\": \"Cable\",\r\n  \"timeout\": \"3600\",\r\n  \"runs\": \"3\",\r\n  \"firstViewOnly\": \"false\"\r\n}"},"comment":{"url":"https://api.github.com/repos/sitespeedio/sitespeed.io/issues/comments/76050133","html_url":"https://github.com/sitespeedio/sitespeed.io/issues/596#issuecomment-76050133","issue_url":"https://api.github.com/repos/sitespeedio/sitespeed.io/issues/596","id":76050133,"user":{"login":"soulgalore","id":540757,"avatar_url":"https://avatars.githubusercontent.com/u/540757?v=3","gravatar_id":"","url":"https://api.github.com/users/soulgalore","html_url":"https://github.com/soulgalore","followers_url":"https://api.github.com/users/soulgalore/followers","following_url":"https://api.github.com/users/soulgalore/following{/other_user}","gists_url":"https://api.github.com/users/soulgalore/gists{/gist_id}","starred_url":"https://api.github.com/users/soulgalore/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/soulgalore/subscriptions","organizations_url":"https://api.github.com/users/soulgalore/orgs","repos_url":"https://api.github.com/users/soulgalore/repos","events_url":"https://api.github.com/users/soulgalore/events{/privacy}","received_events_url":"https://api.github.com/users/soulgalore/received_events","type":"User","site_admin":false},"created_at":"2015-02-25T20:33:35Z","updated_at":"2015-02-25T20:33:35Z","body":"Hi @Vandrix, yes I know about the problem (we have it on the FAQ and https://github.com/tobli/browsertime/issues/70). What happens is that Chrome/Chromedriver fails, and right now we are not able to catch/recover. We have it reported to Selenium (we use it internally) and they have been able to reproduce. https://code.google.com/p/selenium/issues/detail?id=8261\r\n\r\nHowever, the main problem for us is that when Chrome fails, we aren't able to recover. We are working on a fix (meaning skipping the Selenium NodeJS version, because handling errors could be easier/better). We will probably start testing the new solution early next week. I'll keep you updated.\r\n\r\nBest\r\nPeter\r\n\r\n\r\n"}}