No inspectable targets about html-pdf-chrome HOT 7 CLOSED

Ditto. It works a few times in a row, and then out of the blue this error appears.

If I restart google-chrome it works again.

I get the bug both on Mac and on Ubuntu.

from html-pdf-chrome.

Possibly related to this issue (using chrome-remote-interface wrong?):
cyrus-and/chrome-remote-interface#136

from html-pdf-chrome.

I've seen this issue often enough during the automated tests on the CI servers. My plan was to try and expose the Chrome logs to see if anything wonky was going on there. As far as I know, we're using chrome-remote-interface correctly. We always make sure to close any connection to Chrome when finished. (https://github.com/westy92/html-pdf-chrome/blob/master/src/index.ts#L85)

As of right now, each PDF generation opens up a connection with Chrome and closes it when finished, which does not allow for parallelization. I'm hoping to revamp the API in v1 so that we open up one persistent connection with Chrome and we can reuse to allow parallelization. (#14)

from html-pdf-chrome.

@westy92 Actually that error pops up when I tried the recommended approach from the README.md of keeping chrome always running.

I just tried to use the built in chrome-launcher mechanism and it seems to "solve" the issue (no more error) while adding some overhead.

Obviously it isn't a solution because it adds unnecessary overhead.

from html-pdf-chrome.

I think this happen when we try to generate 2 pdf on the same instance with no delay between call.

from html-pdf-chrome.

Could you please verify this is still an issue with the newly-published v0.4.1?
@GautierT @israelidanny @ndaiya

from html-pdf-chrome.

Closing due to inactivity and inability to reproduce since v0.4.1. Please add more information if you are able to produce the issue again! Thank you.

from html-pdf-chrome.