Slow startup (Mac only?)

[GoogleCodeExporter]

On Chrome 4.0.288.1 / OSX 10.6.2 / Macbook Pro 2.4GHz it takes 
between 5 and 10 seconds for rikaikun to start working (and the "on" tag to 
appear) after clicking the toggle button.

After that, everything seems to work fine.

I currently don't have a Windows installation available, but a short test on 
Linux didn't exhibit this behavior. I assume it's Mac-specific.

Cheers,
Martin

P.S.: Glad someone ported rikaichan to Chrome. Thanks and keep up the 
good work.

Original issue reported on code.google.com by lindonaa...@gmail.com on 8 Jan 2010 at 12:07

[GoogleCodeExporter]

I am on windows and the time between clicking and seeing the "on" tag is about 
3 seconds. Also, it lags sometimes over text for 1-2 seconds. I also saw a slow 
start when using 
rikaichan in firefox. It could be computer specific

Original comment by derekAthomas@gmail.com on 9 Jan 2010 at 2:54

[GoogleCodeExporter]

Yeah, it seems like it's probably computer specific.  The stuff rikaikun/chan 
do on 
start up involves reading in a lot of text and the look up process can be 
intensive as 
well.  If the system is bogged down at all there can be delay.

I'll try to progressively optimize as the project goes on so everyone has a 
decent 
experince.

Original comment by melin...@gmail.com on 9 Jan 2010 at 4:04

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

This occurs on an otherwise idle machine. Also only on OSX - loading rikaikun 
on 
Chrome for Windows or Linux (in VMs on the very same notebook) is significantly 
faster 
(about factor 2 to 3).

Well, maybe Chrome's OSX port is somehow to blame. It's still a bit "rough 
around the 
edges" .. especially the dev channel builds.

Original comment by lindonaa...@gmail.com on 9 Jan 2010 at 4:43

[GoogleCodeExporter]

The loading process involves reading in reasonably large dictionary files into 
the 
browser, but it's usually only a few seconds max when bogged down.

I definitely agree the level you're seeing on OSX is something special, I'll 
have to 
see if it gets better in future versions.

I work mostly on a PC so testing this myself is difficult.  I'll try in the 
next few 
days to ensure that it's consistent, and if it is, I'll file a bug with Google.

Original comment by melin...@gmail.com on 9 Jan 2010 at 4:54

[GoogleCodeExporter]

Thanks for looking into this. Fortunately the extension works quite well after 
the initial 
lag, so it's only a minor annoyance anyways.

Out of curiosity I gave it a try with the latest Chromium nightly (4.0.295.0 
(35874)), but 
that doesn't seem to change anything.

Original comment by lindonaa...@gmail.com on 9 Jan 2010 at 5:09

[GoogleCodeExporter]

This really tricked me the first time I tried to use it...couldn't figure out 
how to make it 
work.  >.<
Maybe list somewhere on the download page that you have to click the button, 
and then 
in some instances wait a while for it to be ready?  Took me about 10 minutes to 
figure it 
out...  Even once the box pops up saying it's enabled, it still takes a few 
seconds before 
it works, so I kept thinking it was broken.

Original comment by locod...@gmail.com on 23 Feb 2010 at 4:39