-
Notifications
You must be signed in to change notification settings - Fork 8
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
Saving changes to address book results in ISI #39
Comments
This bug also occurs on my X1000 and is what prevents me from updating SimpleMail from v.42 to v.45. Versions newer than .42 all have this issue. I know several other people who will not upgrade from v.42 due to this issue. It's a critical issue. |
confirmed on my aros compile. trying to look into it. |
seems to happen in addressbook_clear() called from void addressbookwnd_store(void) in addressbookwnd.c (ln 1304). because this function has been called once before from line 495 of the same file with no problem i dont think this is the problem in function implementation in platform agnostic code but some problem in mui interface. |
Hmm...I've had it crash when you click Ok on the dialog when you add a email address. Here is the stack trace. Crash log for task "SimpleMail_v45" Stack trace: |
One other observation. If I open the address book and just click on "Save" once it doesn't crash. If I click on "Save" a second time it crashes. I can even click on "Save", close the address book, then open it up again and click on Save and it crashes. Something in the Save code path maybe is trashing something. |
Any attempt to save any changes to the address book results in a fatal ISI. This behavior is observed in all AOS4 builds on my X5000 running AOS4.1 FE update 1. To reproduce:
... and that's it. instant ISI. I am also attaching a GR crashlog to help with debug. This bug still exists in version 0.45.
Crashlog_SimpleMail_2018-06-06_18-45-45.txt
Note: this issue was copied over from https://sourceforge.net/p/simplemail/bugs/182/
The text was updated successfully, but these errors were encountered: