herususanto10121980 / chrometophone

Automatically exported from code.google.com/p/chrometophone
0 stars 0 forks source link

Javascript error on every page load. #316

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
When I open the javascript console, I consistently get this error:

Port error: Could not establish connection. Receiving end does not exist.  
chrome/RendererExtensionBindings:124

This only occurs when I have chrome-to-phone enabled.

Using Chrome 13.0.761.0 dev

Original issue reported on code.google.com by bendavi...@gmail.com on 24 May 2011 at 4:22

GoogleCodeExporter commented 8 years ago
This is happening to me as well. It occurs every time i load (or reload) a 
page, regardless of site or tab. I am using Chrome Version 20.0.1123.4 dev, on 
Fedora 16 x86_64. However, I am getting a different message:

Port error: Could not establish connection. Receiving end does not exist.   
      chromeHidden.Port.dispatchOnDisconnect 

The error location is "miscellaneous_bindings:232"

As a developer, I rely on the console to report the number of JS errors 
accurately. I believe this error is more severe than "Medium", as I have to 
wade through a lot of code in the console to find out my app isn't causing the 
error. Is there any way to add exception handling for this error in the 
extension? Thank you!

Original comment by sty...@mdlogix.com on 10 May 2012 at 5:57

GoogleCodeExporter commented 8 years ago
Also seeing this problem in Chrome 20.0.1132.3 dev on OSX.

Port error: Could not establish connection. Receiving end does not exist. 
miscellaneous_bindings:232
chromeHidden.Port.dispatchOnDisconnect miscellaneous_bindings:232

The suggested solution to a similar problem posed on SO is to use a background 
page instead of a background script.  See:

http://stackoverflow.com/questions/9106519/port-error-could-not-establish-connec
tion-receiving-end-does-not-exist-in-chr

I'd love to be able to eliminate this error from my javascript console on every 
page! :-)

Original comment by mark.tit...@gmail.com on 19 May 2012 at 2:19

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
This is happening to me as well.

Original comment by PHOENIX....@gmail.com on 28 Jun 2012 at 7:17

GoogleCodeExporter commented 8 years ago
my chrome version: 20.0.1132.43 m on win32

Original comment by PHOENIX....@gmail.com on 28 Jun 2012 at 7:17

GoogleCodeExporter commented 8 years ago
don't open Developer Tools windows can resolve this problem!
I think it use the port which communicates.

Original comment by PHOENIX....@gmail.com on 28 Jun 2012 at 7:24

GoogleCodeExporter commented 8 years ago
Same problem here with both Google Chrome to Phone and Chrome to Windows Phone.

Original comment by olejo...@gmail.com on 6 Jul 2012 at 6:02

GoogleCodeExporter commented 8 years ago
Looks like a dup of issue 451

Original comment by fredsa@google.com on 25 Jul 2012 at 8:46

GoogleCodeExporter commented 8 years ago
Happening on C2P 2.3.1 on Ubuntu 12.04 with Chrome 20.0.1132.57.

Annoying bug as the console is littered with this on every page. 

Original comment by HealthyE...@gmail.com on 28 Jul 2012 at 1:47

GoogleCodeExporter commented 8 years ago
20.0.1132.57 on OSX 10.7.4 too

Original comment by vaughan....@gmail.com on 28 Jul 2012 at 5:14

GoogleCodeExporter commented 8 years ago
Windows 7 x64 dev environment here, chrome 21 

It's definitely a bug with Chrome to Phone. Upon disabling Chrome to Phone the 
port error went away. I tried multiple variations of disabling, uninstalling, 
etc and my findings seem consistent. 

Original comment by Christop...@gmail.com on 3 Aug 2012 at 5:55

GoogleCodeExporter commented 8 years ago
Same problem here:

Port error: Could not establish connection. Receiving end does not exist.
chromeHidden.Port.dispatchOnDisconnect
miscellaneous_bindings:232

Only occurs, when Chrome to Phone is activated.

Google Chrome Version 21.0.1180.81 on Ubuntu Linux
Google Chrome to Phone Extension 2.3.1

This is really annoying, because I need my console for development (and this 
makes it near unusable) while I was going to use Chrome to Phone to send URLs 
to my Andoid to test them in the various browsers there. Now it seems like I 
would have to choose... Please fix more than a year old bug!

Original comment by marcloehe@gmail.com on 30 Aug 2012 at 6:36

GoogleCodeExporter commented 8 years ago
I agree. As a web developer, this is very frustrating! Without resolution, this 
extension is removed!

Original comment by fi.x...@gmail.com on 30 Aug 2012 at 7:17

GoogleCodeExporter commented 8 years ago
As mentioned, this also happens in Chrome to Windows Phone, so is it actually a 
Chrome bug?

Original comment by olejo...@gmail.com on 30 Aug 2012 at 7:31

GoogleCodeExporter commented 8 years ago
Chrome to Windows Phone is probably a clone/fork of Chrome to Phone, I guess 
the bug is on the extension and not on Chrome.

To the author of comment #13, do you really think the authors of this extension 
are concerned that you'll stop using it?

Original comment by dsero...@gmail.com on 30 Aug 2012 at 7:39

GoogleCodeExporter commented 8 years ago
I found Chrome to mobile [ 
https://chrome.google.com/webstore/detail/idknbmbdnapjicclomlijcgfpikmndhd ] 
does the job I was using chrome to phone for but without the error. May help 
you if you can run Chrome on your Android device...

Original comment by kel...@kelvinluck.com on 31 Aug 2012 at 1:29

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Original:
issue 316

Duplicates:
issue 451
issue 452
issue 456

64 total votes at time of comment.

Original comment by gic...@gmail.com on 2 Oct 2012 at 6:49

GoogleCodeExporter commented 8 years ago
Original:
issue 316

Duplicates:
issue 451
issue 452
issue 456

64 total votes at time of comment.

Original comment by gic...@gmail.com on 2 Oct 2012 at 6:49

GoogleCodeExporter commented 8 years ago
Same issue. Chrome 23.0.1271.64 beta, OS X Mountain Lion

Original comment by kris.kha...@gmail.com on 8 Nov 2012 at 6:53

GoogleCodeExporter commented 8 years ago
Same problem, very annoying when trying to debug JS pages!

Chrome Version 23.0.1271.64 m\
Windows XP SP3 32bit

Removing the extension eliminated the problem.

Original comment by letsan....@gmail.com on 14 Nov 2012 at 1:34

GoogleCodeExporter commented 8 years ago
same issue!

Original comment by marco.gi...@gmail.com on 20 Nov 2012 at 4:14

GoogleCodeExporter commented 8 years ago
yup.. annoying little error on console..
chromeHidden.Port.dispatchOnDisconnect

Original comment by m...@ryanharne.net on 5 Dec 2012 at 3:38

GoogleCodeExporter commented 8 years ago
+1. Any alternative extension we can use until the devs get around to fixing 
this?

Original comment by benf...@gmail.com on 6 Jan 2013 at 9:00

GoogleCodeExporter commented 8 years ago
+1. the problem is very annoying!

Original comment by masta2ooo on 7 Jan 2013 at 3:44

GoogleCodeExporter commented 8 years ago
I don't think it will be ever resolved...

almost 2 years have passed.

Original comment by giam...@gmail.com on 7 Jan 2013 at 3:50

GoogleCodeExporter commented 8 years ago
Agreed, the don't give a s***t

Original comment by raj.tha...@gmail.com on 7 Jan 2013 at 3:59

GoogleCodeExporter commented 8 years ago
Indeed the Chrome to Mobile extension 
https://chrome.google.com/webstore/detail/chrome-to-mobile/idknbmbdnapjicclomlij
cgfpikmndhd works like advertised.

It's also made by Google and looks better. Bye bye Chrome to Phone!

Original comment by danielb...@gmail.com on 23 Jan 2013 at 8:25

GoogleCodeExporter commented 8 years ago
 But it doesn't work with the stock browser, right?

Original comment by olejo...@gmail.com on 23 Jan 2013 at 8:35

GoogleCodeExporter commented 8 years ago
Chrome 26.0.1410.43 on Windows 8 x64 with the latest Chrome to Phone extension 
installed.

Every page refresh of certain websites produces missing CSS/Scripts on the 
page, and the following error in the console:

chromeHidden.Port.dispatchOnDisconnect

Disabling the Chrome to Phone extension resolves the issue.

Original comment by ka...@markowicz.info on 3 Apr 2013 at 4:32

GoogleCodeExporter commented 8 years ago
This is such a ridiculous issue.  Good work at being lazy devs and losing 
users. 

Original comment by staticf...@gmail.com on 24 Apr 2013 at 11:39

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
Okay, I've waited for too long. Time to remove this extension.

Original comment by kSolad...@gmail.com on 29 Apr 2013 at 2:04

GoogleCodeExporter commented 8 years ago
Okay, I've waited for too long. Time to remove my subscription to this issue.

Original comment by bogdan.b...@gmail.com on 29 Apr 2013 at 2:36

GoogleCodeExporter commented 8 years ago
yeah me too!

Original comment by giam...@gmail.com on 29 Apr 2013 at 2:37

GoogleCodeExporter commented 8 years ago
Does anyone know of a similar program/extension to this?

Original comment by UnPlan2...@live.at on 29 Apr 2013 at 2:39

GoogleCodeExporter commented 8 years ago
Try chrome to mobile--I have only seen this js error once with that
extension, but it's much better.

Original comment by staticf...@gmail.com on 29 Apr 2013 at 5:58

GoogleCodeExporter commented 8 years ago
sadly it works only for android 4

Original comment by giam...@gmail.com on 30 Apr 2013 at 7:39

GoogleCodeExporter commented 8 years ago
Chrome to mobile doesn't work if you use the stock browser on your phone. Even 
though Chrome has sync and a better UI in many ways, the stock browser is still 
performing better on my Galaxy Nexus in almost every way.

Original comment by olejo...@gmail.com on 30 Apr 2013 at 10:11

GoogleCodeExporter commented 8 years ago
Did you install the app? It won't just work outright with the stock
browser, you need to install the app and connect it to your gmail account.

Comment #39 on issue 316 by olejo...@gmail.com: Javascript error on every
page load.
http://code.google.com/p/**chrometophone/issues/detail?**id=316<http://code.goog
le.com/p/chrometophone/issues/detail?id=316>

Chrome to mobile doesn't work if you use the stock browser on your phone.
Even though Chrome has sync and a better UI in many ways, the stock browser
is still performing better on my Galaxy Nexus in almost every way.

Original comment by staticf...@gmail.com on 30 Apr 2013 at 12:25

GoogleCodeExporter commented 8 years ago
time to remove this extension and app.

Original comment by rush....@gmail.com on 7 May 2013 at 2:21

GoogleCodeExporter commented 8 years ago
I also have found that the only solution is to uninstall the android app and 
this extension. Luckily there are other, similar solutions.

Also, we're nearly at the two year anniversary of this bug.

Original comment by johnny.k...@gmail.com on 10 May 2013 at 4:42