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.

Launchservices causes timeout discovering browsers on OSX

See original GitHub issue

Describe the bug Debugging via chrome appears to broken after upgrade.

To Reproduce Steps to reproduce the behavior:

Goto debug section
Click settings and add basic Launch Chrome
Click run
See error:

Error processing launch: Error: Could not attach to main target
	at Object.t.timeoutPromise (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js:1:33028)
	at f.prepareLaunch (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js:15:2619737)
	at processTicksAndRejections (internal/process/task_queues.js:85:5)
	at async f.launch (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js:15:2620329)
	at async t.Binder.captureLaunch (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js:73:25637)
	at async t.Binder._launch (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js:73:25208)
	at async Promise.all (index 6)
	at async t.Binder._boot (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js:73:24468)
	at async t.default._onMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/extension.js:15:2459238)

Log File

Gz json file seems to be corrupt.

VS Code Version: 1.47.0

Additional context MacOSX

Issue Analytics

State:
Created 3 years ago
Reactions:4
Comments:18 (9 by maintainers)

Top GitHub Comments

6reactions

connor4312commented, Jul 10, 2020

This will be fixed in today’s nightly build (published at 5 PM PST). Thank you for your help in diagnosing this!

4reactions

connor4312commented, Jul 10, 2020

Yea, the previous debugger just probed pre-set paths. The downside is that if you have the browser installed on some non-default path, you would of course need to fiddle with configuration. But we could also do the probing to provide fast launches for common cases

Top Results From Across the Web

Continuous internet browser timeouts - Apple Community

Hi, I've been getting a weird slow down problem when browsing the Internet with either Safari or Firefox that seems to be a...

Error: Could Not Attach To Main Target - ADocLib

Ask questionsLaunchservices causes timeout discovering browsers on OSX. Describe the bug Debugging via chrome appears to broken after upgrade. Error processing ...

Fixing Wi-Fi “Connection Timeout Occurred” Errors on Mac OS X

WiFi connection looked normal and “internet reachable” shown, but no internet connection via any browser on 10.11.5 Knew internet connection ...

Oracle® Endeca Information Discovery Integrator

Oracle® Endeca Information Discovery Integrator : Integrator Server ... This may cause CloverETL Server logging to be ill-configured.

SSL timeout on some sites, across all browsers, on Mac OS X ...

I get this specific error in Google Chrome, but the same problem occurs in both Safari and Firefox. Other sites work fine, and...