Skip to content

Kanji drawing search after switch to open app fails, requires app close #547

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kcroker opened this issue Aug 22, 2015 · 8 comments
Closed
Labels

Comments

@kcroker
Copy link

kcroker commented Aug 22, 2015

If you switch to Aedict from some other app (Anki in my case) while Aedict was already instantiated, the stroke kanji search fails with the following message: Failed to find kanjis, a

@kcroker
Copy link
Author

kcroker commented Aug 22, 2015

Failed to find kanjis: android.os.DeadObjectException

@mvysny
Copy link
Owner

mvysny commented Aug 23, 2015

Thank you for letting me know, and I apologize for this behavior. I will try to reproduce the issue myself, please stay tuned.

@mvysny mvysny added the bug label Aug 23, 2015
@kcroker
Copy link
Author

kcroker commented Aug 23, 2015

The issue seems to have gone away with a dictionary update, so that may be
a clue :)

Again, amazing program! I bought the stroke drawing program even though I
don't need it, so that I could pay you in some way since you refuse paypal
donations!
On Aug 23, 2015 4:31 PM, "Martin Vysny" notifications@github.com wrote:

Thank you for letting me know, and I apologize for this behavior. I will
try to reproduce the issue myself, please stay tuned.


Reply to this email directly or view it on GitHub
#547 (comment).

@kcroker
Copy link
Author

kcroker commented Aug 24, 2015

The bug persists even with up to date dictionaries: newest Nexus 5 stock
Android.
On Aug 23, 2015 4:31 PM, "Martin Vysny" notifications@github.com wrote:

Thank you for letting me know, and I apologize for this behavior. I will
try to reproduce the issue myself, please stay tuned.


Reply to this email directly or view it on GitHub
#547 (comment).

@mvysny
Copy link
Owner

mvysny commented Aug 24, 2015

Well, I do not reject donations per se ;) I will gladly accept the donations via PayPal, my mail address is vysny@baka.sk. Any support is highly appreciated. Let me look at this pesky issue. Meanwhile, it would be of tremendous help if you could obtain the stack trace information bound to that DeadObjectException. This would require you to install Android SDK - would you be interested in doing that? You can find more information here: http://aedict.eu/faq.html, the "Aedict 3 log" section.

@mvysny
Copy link
Owner

mvysny commented Aug 25, 2015

Unfortunately I cannot reproduce this issue myself. I can try to perform a blind fix, but first I would perhaps try to reproduce the issue. Can you please describe in more depth, how exactly are you switching to Aedict from some other app? I tried both sharing selected text to Aedict and activating the persistent notification message, but I get no DeadObjectException. Perhaps the KanjiPadExt service is killed by your phone during the drawing lookup, because of low memory? What kind of phone do you have, and how much memory does it have?
In order to do the blind fix, I will need the stack-trace of the DeadObjectException exception though - can you please install the Android SDK, obtain the log and paste it here?

@mvysny
Copy link
Owner

mvysny commented Aug 25, 2015

Aha! Reproduced ;) If the search service is killed, the client will start failing with DeadObjectException.

@mvysny
Copy link
Owner

mvysny commented Aug 25, 2015

Fixed in Aedict 3.32, please reopen if Aedict fails again.

@mvysny mvysny closed this as completed Aug 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants