Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Bug with headless Chrome

See original GitHub issue

Sometimes, when I try run reference or test, chrome has been crashed. In terminal i receive message about successes operation. But, if reference was run, app doesn’t created reference images, if test was run, app create next report: In this instance Chrome satays at system processes. If it don’t remove manually, next operations with backstopjs will failed.

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:8 (3 by maintainers)

Top GitHub Comments

2reactions

garriscommented, Feb 14, 2018

Also, please update your backstop — we released a new version (3.1.15) yesterday that should address this bug.

1reaction

SheffBRCcommented, May 21, 2018

Bug depend on hardware. Bug was at mac mini 2014 with HDD

There are no problems at MacBook with I5 2.3 Ghz, 8 Gb RAM and SSD

Top Results From Across the Web

Bug? with headless chrome and remote-debugging option

I believe it's because chromedriver uses the remote debugging functionality to do its thing, and chrome only supports one remote debugging client. https://bugs....

Security: Clickjacking RCE of Chrome headless with Remote ...

It is possible to compromise a local machine running an instance of Chrome headless with remote debugging enabled through a combination of ...

[BUG] Chrome Headless Clipboard issue #19038 - GitHub

We have this function, which is a tooltip, which copies text clipboard, this fails on headless chrome but works on headed. Works on...

Getting Started with Headless Chrome - Chrome Developers

Headless Chrome is shipping in Chrome 59. It's a way to run the Chrome browser in a headless environment. Essentially, running Chrome ...

Chrome Headless Browser Issue - Bugs Report

Hi Team. The Chrome Headless browser was unable to identify the element even it is mentioned with id in the test case.