gwuhaolin / chrome-pool Goto Github PK

chrome-remote-interface update to 0.24.0

我起了一个web服务，创建了一个chromepool对象，在访问web服务的时候，生成tab和protocle，然后完成请求后，release掉，当我频繁访问web服务的时候，会有很大的几率有not open报错，如果我不release，就一切正常，这儿有个类似的bug
cyrus-and/chrome-remote-interface#189

当我在centos7下面运行ChromePool.new()的时候，会报错：
(node:30838) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 101 chromeAlive listeners added. Use emitter.setMaxListeners() to increase limit
不管listenner数量设为多少，我发现listenner会一直增长直到报错，还有就是pool源代码里面执行到
chromePoll.chromeRunner = await launchChrome(Object.assign({}, chromeRunnerOptions, { port }));
就不执行了，看来是runner那边有bug

就是runner里面的一些参数 比如chromeFlags

chrome-remote-interface has update to 0.24.3, and only the newest version support capture clip screenshot.

A Node library which provides a high-level API to control headless Chrome over the DevTools Protocol made by google.
https://github.com/GoogleChrome/puppeteer
谷歌自己出了个

我之前从 https://chromedevtools.github.io/devtools-protocol/ 看到：

Simultaneous protocol clients
We currently do not support multiple clients connected to the protocol simultaneously. This includes opening DevTools while another client is connected. On the bug tracker, crbug.com/129539 follows the issue; you can star it for email updates.

我的理解是一个headless chrome只能支持一个web socket client接入，理论上不可能控制多tab？