search

amostl / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Cannot connect to Google Chrome on Mac #27

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Google Chrome version: 5.0.342.7 beta
SDK + Eclipse Debugger version(s): 3.5.2
OS + version: Mac OS X 10.5.x and 10.6.x

What steps will reproduce the problem?
1. Download latest Chrome Developer Tools from SVN
2. Establish debug session as outline on main project page

What is the expected result?
Prompt to select browser tab is shown.

What happens instead?
Connection takes forever and ends with "Timeout" exception from V8Helper.

The very same code works without any problems on Windows. The debugger was 
working before and it suddenly stopped 
working on all Mac machines.

There was a Chrome version update this week and it looks like it broke the 
debugger (we were testing debugger on 
Chrome all this time and it was working great). I tried to research the code 
and it looks like the connection is 
established, "version" request is sent but no response is ever received.

Original issue reported on code.google.com by eostrouk...@gmail.com on 26 Mar 2010 at 10:52

GoogleCodeExporter commented 9 years ago 
I have the same issue. I tried the latest Chromium build from 3/31 (5.0.367.0 
(43218)) and so far it seems to be 
working OK there.

Original comment by dpodwall on 31 Mar 2010 at 7:21

GoogleCodeExporter commented 9 years ago

Original comment by peter.ry...@gmail.com on 1 Apr 2010 at 8:11

GoogleCodeExporter commented 9 years ago 
This should be a temporary issue. It should be fixed in the next build.

Original comment by peter.ry...@gmail.com on 3 Apr 2010 at 3:59

GoogleCodeExporter commented 9 years ago 
You can check out the following table:

http://code.google.com/p/chromedevtools/wiki/VersionCompatibility

Original comment by peter.ry...@gmail.com on 7 Apr 2010 at 5:37

GoogleCodeExporter commented 9 years ago 
Does this mean we would need to require our users to update the product as 
Chrome gets 
updated?

Original comment by eostrouk...@gmail.com on 7 Apr 2010 at 5:41

GoogleCodeExporter commented 9 years ago 
This is only a recommendation. As a general practice the most recent version is 
recommended.

In fact there might be a moment when future version of Chrome stops supporting 
the 
current protocol and old versions of plugins will stop working. However we 
don't have 
such plans for a near future AFAIK.

Original comment by peter.ry...@gmail.com on 7 Apr 2010 at 5:58

GoogleCodeExporter commented 9 years ago 
I believe this one can be closed now - it works with the latest beta.

Original comment by eostrouk...@gmail.com on 8 May 2010 at 12:26

GoogleCodeExporter commented 9 years ago 
Updated version for Mac works OK

Original comment by peter.ry...@gmail.com on 9 Aug 2010 at 6:12