On Sun, Jun 24, 2012 at 10:01 PM,
<vbh...@gmail.com> wrote:
Hi,
I have been trying to get chrome remote debugging working without success. The diagnosis I have done so far points me to some bugs in DevTools.js in chrome (I might be wrong!). The scenarios I have tried are the following:
- On Linux: As described here, I opened chrome with --remote-debugging-port=9222 and another instance of chome with --user-data-dir option. The second instance opens in the same chrome window but a different tab.
Either I misunderstand your description or your description indicates a problem with your set up.
Try using does different values of --user-data-dir on the command line for each of two different Chrome instances. They cannot share windows.
- When I point this new tab to, http://localhost:9222/, I get the small tiles with inspectable pages, but upon clicking on any of them the page just keeps waiting, never loads. At this time if I have the developer tools open, I can't see anything about why the browser is waiting.
Open devtools on devtools and look at the Console panel. (Right click on the panel selection bar if you can't get the key bindings to work).
- If I open, http://localhost:9222/ using Firefox 13, I get this error: "[21:51:12.254] WebInspector._currentFocusElement.focus is not a function" and another error: "[21:51:12.625] Firefox can't establish a connection to the server at ws://localhost:9222/devtools/page/0". I have checked that this version of Firefox supports websockets and I have them enabled, so not sure why this might be happening.
I don't know that anyone tests this use, so I'm not surprised if this does not work.
- I started debug instance of Chrome on a remote machine and set up a tunnel as suggested here to access the remote debugging page from a completely different instance of Chrome (local machine). Even this run led to the same result as the first case.
- I even tried the above points on Windows.
I am completely befuddled and would be really thankful for any help.
Thanks,
Bhanu