"Force close" shortly after snoozed alarm triggers about kraigsandroid

[GoogleCodeExporter]

Thanks for the detailed bug report.  The stack traces is the log output are 
really helpful.

A couple other people have reported this problem as well over the past couple 
weeks.  I haven't been able to reproduce it yet, but I finally managed to get a 
stack trace of the problem from someone earlier this week.  It seems to match 
up with the one you linked to.

I think there's a race condition in the notification code that triggers when 
the garbage collector is triggered at the same time as the alarm.  The app 
hasn't changed since last summer, so I'm still not sure why this seems to me a 
more common problem now.

Regardless, I put together an apk with a change that I think should fix it, but 
I haven't heard back from anyone yet.  Feel free to give it a try.
http://kraigsandroid.googlecode.com/files/Alarm%20Klock.apk

Thanks again,
Craig

Original comment by [email protected] on 19 Feb 2011 at 5:26

• Changed state: Accepted

[GoogleCodeExporter]

Thanks for the pointer/fix (and AlarmKlock generally).  I can no longer 
reproduce the problem having installed that new APK over the top of 1.6, so 
perhaps no news is good news.  I'll carry on using it as my daily alarm and 
report here if it happens again.

Has the repository moved?  I don't see the changeset listed at 
http://code.google.com/p/kraigsandroid/source/list .

Curious that it should only manifest itself now.  The most complicated and 
sensational explanation is normally the correct one, so I'm going to assume 
it's an elaborate Chinese trojan specifically targeting lethargic students like 
me in a long-term cyberwar effort to stifle innovation by the West.

Original comment by [email protected] on 19 Feb 2011 at 7:16