Closed GoogleCodeExporter closed 9 years ago
Hmm, it's hard to say what could be the problem in an isolated case like this.
Rikaikun hasn't changed of course so it's tough to see what could be causing
it. Maybe low memory? Seems unlikely.
If you know how (or could look up) how to look at the javascript console in the
Chrome developer tools when you click on the icon the first time it might show
some errors that could be useful.
Sorry I couldn't be of more help.
Original comment by melin...@gmail.com
on 2 Oct 2012 at 12:55
I have the same OS, Chrome version, and Rikaikun version and also have the
issue.
The only thing I've managed to capture in the console is the following message:
Uncaught TypeError: Cannot read property 'style' of null
/p/rikaikun/issues/detail?id=80&colspec=ID%20Type%20Status%20Priority%20Stars%20
Milestone%20Owner%20Summary:637
Original comment by dominic....@gmail.com
on 2 Oct 2012 at 1:07
Dominic,
The error is just some problem with this page not the extension. Darn.
Did it also start this morning for you? Was there a recent windows or chrome
update I wonder?
It'd be strange if it was a chrome update though since I test the new releases
before they're launched to everyone and haven't seen this problem.
I'll keep thinking and be sure to tell me if you guys think of anything else.
Original comment by melin...@gmail.com
on 2 Oct 2012 at 1:11
Unfortunately, I get absolutely no output in the console on either of the
clicks.
Original comment by shimanotaka
on 2 Oct 2012 at 1:17
Hi,
I only found the extension late last week, and it has been doing it ever since
- so I can't really say if it's a recent Chrome update, sorry.
Original comment by dominic....@gmail.com
on 2 Oct 2012 at 1:24
This also crashes Rikaikun:
1. Open chrome://chrome/extensions/
2. Open "Inspect views: background.html" for Rikaikun
3. Click the Rikaikun icon once
4. Click the "Sources" tab in the background.html popup window.
Still couldn't get any output in the console though.
Original comment by shimanotaka
on 2 Oct 2012 at 1:31
Now Rikaikun is working again. I rebooted my computer yesterday so that might
have been what "fixed" it.
Original comment by shimanotaka
on 3 Oct 2012 at 2:32
Working for me too, sorry - I was sure I had already tried that.
Original comment by dominic....@gmail.com
on 3 Oct 2012 at 7:42
I'm just glad it's working again.
Original comment by melin...@gmail.com
on 3 Oct 2012 at 10:54
It's crashing again. Same as before. Any chance of building some kind of
debugging function into Rikaikun? Might be that a reboot will fix it again, but
rebooting the computer everytime isn't really a good long-term solution.
Original comment by shimanotaka
on 10 Oct 2012 at 8:41
On the extension side, all javascript is debuggable through chrome via the
javascript console. The problem is I can't recreate the problem and there are
no obvious errors that are showing up it seems. I assume over time something
is changing in the OS which is fixed by a restart and that is causing rikaikun
to fail.
It's hard to imagine errors which cause the extension to crash but not print
some error so maybe I'll see if a log is generated somewhere.
Original comment by melin...@gmail.com
on 10 Oct 2012 at 12:57
Original issue reported on code.google.com by
shimanotaka
on 2 Oct 2012 at 12:45