Javascript error on every page load. about chrometophone HOT 42 OPEN

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!

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! :-)

[deleted comment]

This is happening to me as well.

my chrome version: 20.0.1132.43 m on win32

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

Same problem here with both Google Chrome to Phone and Chrome to Windows Phone.

Looks like a dup of issue 451

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. 

20.0.1132.57 on OSX 10.7.4 too

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. 

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!

I agree. As a web developer, this is very frustrating! Without resolution, this 
extension is removed!

As mentioned, this also happens in Chrome to Windows Phone, so is it actually a 
Chrome bug?

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?

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...

[deleted comment]

Original:
issue 316

Duplicates:
issue 451
issue 452
issue 456

64 total votes at time of comment.

Original:
issue 316

Duplicates:
issue 451
issue 452
issue 456

64 total votes at time of comment.

Same issue. Chrome 23.0.1271.64 beta, OS X Mountain Lion

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.

same issue!

yup.. annoying little error on console..
chromeHidden.Port.dispatchOnDisconnect

+1. Any alternative extension we can use until the devs get around to fixing 
this?

+1. the problem is very annoying!

I don't think it will be ever resolved...

almost 2 years have passed.

Agreed, the don't give a s***t

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!

 But it doesn't work with the stock browser, right?

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.

This is such a ridiculous issue.  Good work at being lazy devs and losing 
users. 

[deleted comment]

Okay, I've waited for too long. Time to remove this extension.

Okay, I've waited for too long. Time to remove my subscription to this issue.

yeah me too!

Does anyone know of a similar program/extension to this?

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

sadly it works only for android 4

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.

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 [email protected]: 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.

time to remove this extension and app.

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.