Ready4Android wrote: > > mahesh Shivananda writes: > > I faced this problem in this scenario: > > > > Due to a check missing, NPE had occurred previously and when > InputDispatcher > tried to post an event to my activity got the error about the channel > being > closed > > > > Hope this helps :) > > > > Hello there, > > I am facing the same issue as the OP. I wonder if its related to a service > of > ours, running in the background (started by our app). The service wakes up > every > 5 minutes, does something (server communication) and then goes back to > sleep via > Thread.sleep (so the service never really "stops"). > > @Mahesh: Could u elaborate on that NPE? If an NPE really was the cause, > shouldnt > that NPE occur in the logfile? Our logfiles don't show any useful evidence > as to > the cause of this error - neither before nor after it appears in the > logfile. > And since we have an UncaughtExceptionHandler attached to our application > class, > there should be no we could be missing out on any NPEs...). > > One thing I noticed though: Usually when it happens we have a few finalize > calls > before that (I put a log statement in our activity classes so I see when > their > finalizers are called). > > Any help would be greatly appreciated. And as the OP I gotta admitt, that > I have > no idea what "fd" means? >
"fd" is standard programmerese for "file descriptor". It's sort of important to know how a computer works to program for it. Android runs on Linux, and "fd" is a standard Linux (and Unix, and Windows) term. -- Lew -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
