UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to reproduce the problem:
1. Start chrome in headless mode (I used: docker: justinribeiro/chrome-headless/latest timestamp: 2018-10-16T22:26:54.595Z)
2. Run load against chrome (Used: open tab, set html content (Page.setDocumentContent), render pdf (Page.printToPDF) x10 tabs async, without any pauses)
3. At some point chrome replies with no pdf but with `{"method":"Inspector.targetCrashed","params":{}}`
4. After that all retries on that tab are useless, it hungs forever
5. If then try to restart script with 10 more tabs and try to do steps above, chrome may just crash itself.

What is the expected behavior?
May be it is too much, but there was an idea of using chrome as a service. A highload one.

What went wrong?
Well, it died.

Did this work before? No 

Chrome version: Google Chrome 70.0.3538.67  Channel: stable
OS Version: Docker
Flash Version: 

Sorry but can't provide original script code it is proprietary and in Scala :( Anyways I think that this should be reproducible even with node js if it ran through bash several times with `&` at the end.
Also in logs there are messages like this (don't seem to be very meaningful):
```
[1026/210615.082830:ERROR:crash_handler_host_linux.cc(442)] Failed to write crash dump for pid 101
[1026/210615.085017:ERROR:crash_handler_host_linux.cc(442)] Failed to write crash dump for pid 133
[1026/210615.086722:ERROR:crash_handler_host_linux.cc(442)] Failed to write crash dump for pid 147
[1026/210615.088241:ERROR:crash_handler_host_linux.cc(442)] Failed to write crash dump for pid 89
Cannot upload crash dump: failed to open
```

If crash dump is broken I may try to rerun this case, dunno if it got untouched from /fd/4
 

Deleted: chrome-crash-dump 1012 KB

chrome-crash-dump 1012 KB View Download