"no internal extension-to-page port"

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Installed Furigana Injector with Google Chrome.
2. Worked for a while.
3. Upon clicking furigana button, doesn't work anymore (perhaps due to 
Chrome update).

What is the expected output? What do you see instead?
- Expect furigana to appear
- See error message:
Extension Alert Furigana Injector
"Programming error: no internal extension-to-page port establish for the 
tab you just clicked"

Which browser are you using, Firefox or Chrome? On what operating system?
- Chrome, Windows 7

Original issue reported on code.google.com by MaximSa...@gmail.com on 2 May 2010 at 2:28

[GoogleCodeExporter]

I've the same problem; When clicking on the furigana injection extension, i've 
receive 
this error.

I'm using Ubuntu LTS 10.04 Kernel 2.6.34 RT.

Original comment by anaclet...@gmail.com on 3 May 2010 at 1:20

[GoogleCodeExporter]

Akira:
   this error occurs when the server replies but the background process can't identify 
the foreground tab that was originally in focus (typically this means the tab 
that you 
were looking at half a second earlier when you pressed the 振 button).

   I think I will set this action instead: when the reply comes and the current tab 
can't be identified by the internal port no, then I'll set it to inject the 
furigana in 
the current foreground tab.

Original comment by akira%ya...@gtempaccount.com on 5 May 2010 at 3:25

• Changed state: Started

[GoogleCodeExporter]

Seems that finding a port for the current tab is not something you can 
guarantee.

Sorry, I don't know how to fix. I will change the error message in the next 
version.

Akira

Original comment by akira%ya...@gtempaccount.com on 5 May 2010 at 5:22

• Changed state: WontFix

[GoogleCodeExporter]

This is not simply an error that occurs occasionally. Furigana Injector for 
Chrome will 
not work at all for me, and I'd imagine it is the same for the other user who 
posted 
here.

Original comment by MaximSa...@gmail.com on 5 May 2010 at 6:03

[GoogleCodeExporter]

This issue is actually because the recent furigana server down in my case and 
many others. The furigana icon appears grey for weeks.

Original comment by innatere...@gmail.com on 5 May 2010 at 7:52

[GoogleCodeExporter]

The furigana server is offline? Crap! I can't resolve this issue- the server is 
local 
to my network and I can't find a problem with the DNS or my local router 
settings. I 
really need to find a host for a backup instance of the server. If someone 
could host 
fi2.yayakoshi.net then that would work straight away for all users who open 
chrome when 
fi.yayakoshi.net is down.

Original comment by akira%ya...@gtempaccount.com on 5 May 2010 at 8:04

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Well, but it's back now. Just after you commented.
Maybe a local dictionary version is still needed for the meantime.

Original comment by innatere...@gmail.com on 5 May 2010 at 8:49

[GoogleCodeExporter]

> Maybe a local dictionary version is still needed for the meantime.

Fair comment. It has to be server-side for Chrome however (no native libs can 
be 
bundled in the extensions), and I decided to do the same for Firefox to avoid 
multi-
platform issues and heavy memory usage. People love it when it works for their 
platform, but for those it doesn't it's frustrating.

A friend suggested that the server-side Firefox version should be a different 
extension. I think there's some merit to that suggestion.

Either the way the first priority is get a secondary server running. If someone 
has a 
good suggestion for a 1Gb RAM virtual server (xen, kvm, whatever) in Japan, 
Korea, or 
west coast USA I'm all ears. Better yet if anyone can run an extra instance of 
Apache 
and will let me build a module from source on their server, please contact.

Original comment by akira%ya...@gtempaccount.com on 5 May 2010 at 9:47

[GoogleCodeExporter]

Yep, it was up for a short time, but it seems to be back down again.
I can't help with servers or anything, but I thought I should mention that.
It's a good service and I can't wait to see see it running smoothly.

Original comment by MaximSa...@gmail.com on 7 May 2010 at 11:53

[GoogleCodeExporter]

Thanks. I appreciate the positive votes when they're cast.

Original comment by akira%ya...@gtempaccount.com on 7 May 2010 at 12:01

[GoogleCodeExporter]

Providing the latest story here.

Now it seems my Chrome would regularly lose the chance getting server 
around midnight(GMT+8 here), and regain it about after morning.
On the other hand, if I never close whole Chrome once I got the server, 
then it would not become offline. So, yes, apparently the server itself and 
the connection to it was not being disrupted.

Any idea of what was going on? Thank you for all updates and efforts.

Original comment by innatere...@gmail.com on 13 May 2010 at 8:59

[GoogleCodeExporter]

Hi innaterebel,
  yes, the server has had further crashes. I've committed to make a debug version of 
the server and find the memory leak, or make a new server completely. Not for a 
few 
weeks at least though.

  The Furigana Injector extension only checks the availability of server once, when 
the first chrome window is opened. A better solution could be programmed, where 
the 
server is checked periodically, but for the moment fixing the server is the 
priority.

Cheers,

Akira

N.B. Will create a new ticket "Fix server crashes caused by mem. leak"

Original comment by akira%ya...@gtempaccount.com on 13 May 2010 at 9:38