After installing SPYBOT software...

[rosemarychhi]

When installing spybot locks the option to open the browser.

[jasonsanjose]

@rosemarychhi can you provide more information about your system setup like OS version and Spybot version? Does Spybot provide any reporting when it blocks an application?

I initially thought a workaround could be manually launching chrome into remote debugging, e.g.

chrome.exe --remote-debugging-port=9222

However, the launch process recently changed on windows (see adobe/brackets-shell#237). I'm not sure how we can trick brackets-shell into attaching to a manually launched chrome anymore. @gruehle or @redmunds I tried the command below Brackets still attempted to open it's own Chrome window.

chrome.exe --user-data-dir=c:\some\temp\path --no-first-run --no-default-browser-check --allow-file-access-from-files --remote-debugging-port=9222 

Reviewed. Tagging medium priority since this blocks the live development workflow and there is no workaround unless spybot can be disabled temporarily.

[jasonsanjose]

Assigned to @gruehle

[rosemarychhi]

Hi :)

My OS: MS Windows 7 Home Premium 64-bits SP1.

The spybot versión : Spybot 2.1 Free edition.

2013/6/7 Jason San Jose [email protected]

Assigned to @gruehle https://github.com/gruehle

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4084#issuecomment-19131757
.

[JeffryBooher]

Adding CEF/TRACKING labels. This is probably fixed in 1750 since debugging is internal

[peterflynn]

@JeffryBooher I don't think 1750 would affect this -- the "remote debugging" referred to above is in the user's Chrome browser process, not in CEF.