Remote debugging does not work

6,367 views
Skip to first unread message

chen...@gmail.com

unread,
Jul 13, 2011, 1:18:43 AM7/13/11
to Google Chrome Developer Tools
Hi,

I followed the instruction in the below link to configure 2 instances
of Chrome (14.0.814.0 dev-m) on Windows 7 - one instance running with
switch --remote-debugging-port=9222, the one instance opens http://localhost:9222.
It always failed with page unresponsive error dialog.

http://code.google.com/chrome/devtools/docs/remote-debugging.html

netstat -a shows there are 4 established TCP connections between port
9222 and other local ports.

Any idea what could go wrong? Was remote debugging tested on Windows
7?

Thanks in advance,
Rebecca

Mikhail Naganov

unread,
Jul 13, 2011, 4:02:36 AM7/13/11
to google-chrome-...@googlegroups.com
Hi,

Sanity check -- can you please confirm that you are using a separate
profile for the second Chrome instance (by specifying --user-data-dir
argument)?

chen...@gmail.com

unread,
Jul 13, 2011, 1:17:09 PM7/13/11
to Google Chrome Developer Tools
Yes, that was the problem. It works fine after I used different
profile. Thanks!

On Jul 13, 1:02 am, Mikhail Naganov <mnaga...@chromium.org> wrote:
> Hi,
>
> Sanity check -- can you please confirm that you are using a separate
> profile for the second Chrome instance (by specifying --user-data-dir
> argument)?
>
>
>
>
>
>
>
> On Wed, Jul 13, 2011 at 09:18, cheng....@gmail.com <cheng....@gmail.com> wrote:
> > Hi,
>
> > I followed the instruction in the below link to configure 2 instances
> > of Chrome (14.0.814.0 dev-m) on Windows 7 - one instance running with
> > switch --remote-debugging-port=9222, the one instance openshttp://localhost:9222.

johnjbarton

unread,
Jul 25, 2011, 8:23:05 PM7/25/11
to Google Chrome Developer Tools


On Jul 13, 1:02 am, Mikhail Naganov <mnaga...@chromium.org> wrote:
> Hi,
>
> Sanity check -- can you please confirm that you are using a separate
> profile for the second Chrome instance (by specifying --user-data-dir
> argument)?
>

I think it would be helpful if the example on
http://code.google.com/chrome/devtools/docs/remote-debugging.html#remote
had this explanation about different --user-data-dir values.

(I'd fix it myself if I knew where...)

jjb

PhistucK

unread,
Jul 26, 2011, 2:08:37 AM7/26/11
to google-chrome-...@googlegroups.com
Since the intention of remote debugging is to, well, debug remotely and not within the same computer, you should not need this flag.
If you use remote debugging within the same computer, this is an 'advanced' (and maybe even not officially supported) feature.
PhistucK

Mikhail Naganov

unread,
Jul 26, 2011, 3:41:29 AM7/26/11
to google-chrome-...@googlegroups.com
I think John is right. We use "localhost" address in the
aforementioned description, and this will require passing
--user-data-dir. I will fix it.
Reply all
Reply to author
Forward
0 new messages