question-mark
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.

with latest chrome, browser is just exiting

See original GitHub issue
not ok 1 Chrome - error
    ---
        message: >
            Error: Browser exited unexpectedly
            Non-zero exit code: null
            Stderr: 
             [0428/112152.254909:ERROR:resource_bundle.cc(767)] Failed to load /Applications/Google Chrome.app/Contents/Versions/58.0.3029.81/Google Chrome Framework.framework/Versions/A/resources.pak
            Some features may not be available.
            
            
        Log: |
            { type: 'error', text: 'Error: Browser exited unexpectedly' }
            { type: 'error', text: 'Non-zero exit code: null' }
            { type: 'error',
              text: '[0428/112152.254909:ERROR:resource_bundle.cc(767)] Failed to load /Applications/Google Chrome.app/Contents/Versions/58.0.3029.81/Google Chrome Framework.framework/Versions/A/resources.pak\nSome features may not be available.\n' }

anyone have any ideas why this happens?

Issue Analytics

  • State:open
  • Created 6 years ago
  • Comments:17 (2 by maintainers)

github_iconTop GitHub Comments

7reactions
searlscommented, Feb 9, 2018

I’m on testem@2.0.0 and I couldn’t get Chrome headless to work locally or on travis until finding @joppa27’s post. Since phantomjs is now unmaintained, it seems like a headless guide that incorporates these flags & packages would be really useful in the README/docs. Do folks agree?

6reactions
JHKennedy4commented, May 15, 2018

Also crashing with the following output:

DEPRECATION: An addon is trying to access project.nodeModulesPath. This is not a reliable way to discover npm modules. Instead, consider doing: require("resolve").sync(something, { basedir: project.root }). Accessed from:   DependencyVersionChecker.NPMDependencyVersionChecker (/data/app/kochiku-worker/shared/build-partition/sq/invoice-fe/node_modules/ember-try/node_modules/ember-cli-version-checker/src/npm-dependency-version-checker.js:11:32)
Could not start watchman
Visit https://ember-cli.com/user-guide/#watchman for more info.
ember-cli-sentry will not be loaded from bower installation
cleaning up...
Built project successfully. Stored in "/data/app/kochiku-worker/shared/build-partition/sq/invoice-fe/tmp/class-tests_dist-f4XmztuR.tmp".
not ok 1 Chrome - error
    ---
        message: >
            Error: Browser failed to connect within 30s. testem.js not loaded?
            Stderr: 
             [0515/184532.964775:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.
            
            DevTools listening on ws://127.0.0.1:46394/devtools/browser/f1139e46-5dbf-4b0e-8791-2739c68e27c2
            Fontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn't take any effect anymore. please remove it from your fonts.conf
            
            
        Log: |
            { type: 'error',
              text: 'Error: Browser failed to connect within 30s. testem.js not loaded?' }
            { type: 'error',
              text: '[0515/184532.964775:ERROR:gpu_process_transport_factory.cc(1007)] Lost UI shared context.\n\nDevTools listening on ws://127.0.0.1:46394/devtools/browser/f1139e46-5dbf-4b0e-8791-2739c68e27c2\nFontconfig warning: "/etc/fonts/fonts.conf", line 146: blank doesn\'t take any effect anymore. please remove it from your fonts.conf\n' }
    ...

1..1
# tests 1
# pass  0
# skip  0
# fail  1
Testem finished with non-zero exit code. Tests failed.

Using the following flags:

args: [
        "--headless",
        "--disable-gpu",
        "--remote-debugging-port=9222",
        "--remote-debugging-address=0.0.0.0",
        "--no-sandbox",
        "--user-data-dir=/tmp"
      ]
Read more comments on GitHub >

github_iconTop Results From Across the Web

Fix Chrome if it crashes or won't open - Computer
First: Try these common Chrome crash fixes · Quit Chrome and reopen it: Windows: Press Ctrl + q. Mac: Press ⌘ + q....
Read more >
Google Chrome Crashing? Here's How To Fix It
Press the keyboard shortcut Alt + F4 keys to exit Chrome. ... From the list of apps, select Google Chrome and right-click on...
Read more >
Why Does Google Chrome Keep Crashing, Freezing, or Not ...
To do so, click the three-dot Menu button at the top-right of Chrome and choose Exit. Then reopen Chrome after a moment and...
Read more >
Top 8 Ways to Fix Google Chrome Closing Automatically on ...
1. Review Browser Extensions · 2. Clear Corrupt Google Chrome Cache · 3. Use Google Chrome Task Manager · 4. Stop Google Chrome...
Read more >
9 Ways to Get Chrome to Stop Crashing - Nira
Open Chrome and go straight to Menu > “More Tools” > “Extensions.” Your extensions will all be laid out there, and each will...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found