Furigana injector crashing Chrome 19.x for Mac

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use Mac version of Chrome 18.0.1025.162
2. Enable Furigana Injector.
3. Crash. Same problem with rikaikun, by the way.

What is the expected output? What do you see instead?
Not crash

Which browser are you using, Firefox or Chrome? On what operating system?
18.0.1025.162 This isn't the only problem I'm having with this latest version. 
Lots of crashing & corruption of profile files.

Please provide any additional information below.
In developer Version 20.0.1096.1 dev the icon doesn't appear, so it can't be 
enabled. I haven't checked the beta version. Thankfully, rikaikan does work.

Original issue reported on code.google.com by herroflo...@gmail.com on 16 Apr 2012 at 6:15

[GoogleCodeExporter]

Sorry, could you clarify- does the Chrome browser crash? It's very, very 
unlikely that Furigana Injector could be doing this. Extensions only work 
within a sandbox, more or less, and F.I. is not using any of the more recently 
developed extension APIs that might be buggy?

I use Chrome 18.0.1025.142 on Ubuntu myself and don't have the issue.

Original comment by akira.kurogane@gmail.com on 19 Apr 2012 at 5:55

• Changed title: Furigana injector crashing. (crashing what?)
• Changed state: Accepted

[GoogleCodeExporter]

Original comment by akira.kurogane@gmail.com on 19 Apr 2012 at 5:55

[GoogleCodeExporter]

The browser itself was crashing. The same thing happend when I enabled
Rikaichan. This happened even after I deleted Chrome and my Chrome
profile on Mac OS X 10.7.3. I then installed the beta version (I'm
currently using 19.0.1084.30 beta), where the Furigana Injector does
not appear ever, even when viewing pages in Japanese. But Rikaichan
works fine.

It might only be an issue with OS X. I'm using the latest version on
my PC where there is no problem whatsoever.

Original comment by herroflo...@gmail.com on 19 Apr 2012 at 8:22

[GoogleCodeExporter]

I'm sorry, I don't have a Mac. Recently I don't even have a Windows PC either. 
I suspect it's Chromium bug which will get patched.

Maybe you could try to view the javascript console output when you open a 
japanese page? Javascript errors show which file they occurred in, which in the 
case of Furigana Injector will be something like 
"chrome://cbahnmcliajmanjkaolemjelphicnein/kanji_content_detect.js". Hard for 
me to ask you that when the whole browser is crashing, though.

("cbahnmcliajmanjkaolemjelphicnein" is just a more-or-less random id code that 
was given to F.I. when it was uploaded to the Chrome Extensions site.)

Original comment by akira.kurogane@gmail.com on 19 Apr 2012 at 9:34

• Changed title: Furigana injector crashing Chrome 19.x for Mac

[GoogleCodeExporter]

Does this help?

http://pastie.org/3815672

From this page:
http://ja.wikipedia.org/wiki/Wikipedia:%E3%82%A6%E3%82%A3%E3%82%AD%E3%83%9A%E3%8
3%87%E3%82%A3%E3%82%A2%E3%81%AB%E3%81%A4%E3%81%84%E3%81%A6

The only extension I have running is Furigana Injector.

Google Chrome Version 19.0.1084.30 beta

Original comment by herroflo...@gmail.com on 19 Apr 2012 at 9:42

[GoogleCodeExporter]

That's one of the scripts in F.I., yes, but I meant the console area where 
javascript errors appear (and where you can execute javascript expressions in 
realtime). The console seems to be hidden by default. The button for it is in 
the bottom left, inbetween the window icon and the magnifying icon.

(That wiki page is good test page by the way. No problems there.)

Original comment by akira.kurogane@gmail.com on 19 Apr 2012 at 12:36

[GoogleCodeExporter]

I might have just wasted your time. For fun, I deleted the beta and
replaced it with version 18.0.1025.163, deleted my cache, an now FI is
working fine. Perhaps the problem was corrupt files in my cache. The
Javascript console is also working now.

Original comment by herroflo...@gmail.com on 19 Apr 2012 at 2:35

[GoogleCodeExporter]

It may be that it's a bug in the browser beta version that will be resolved. I 
would certainly like to think so. I can't install the beta with otherwise 
screwing up my dev environment for non-F.I. work, so I'm just going to close 
this now.

Regards,

Akira

Original comment by akira.kurogane@gmail.com on 20 Apr 2012 at 1:45

• Changed state: WontFix