i have seen things like that, myself. could you, by any chance, provide us with the logs of the memory leak ?
it might not even be necessary to call unbind(), because you can call the service's thru the obtained interface without being bound to it. (btw, the general problem class is still unfixed on my side as well) On Jan 13, 2:00 pm, Abraham <[email protected]> wrote: > HI All, > > I'm facing an issue with my application & need your expert opinion in > resolving the issue. > > My app has a local service which is started by calling startService() > when the phone boot up is complete. My app also has a UI component > which the user can use for making use of the service. Following the > Local service binding example in ApiDemos my app is calling bindService > () api to bind with the local service & make use of the local service > instance obtained through the IBinder in onServiceConnected() to > perform operations provided by the service. Once the operation is > completed my app calls unbindService() to disconnect the UI from the > service. From this point on my app cannot communicate with the local > service by calling bindService() or startService(). > > Has anyone faced similar issues. If yes, what is the work around. Am I > doing something wrong. > > Another observation is that if I donot call unbindService() I'm able > to make use of the operations provided by the service, although it > leads to memory leaks ( as displayed in the logs) . > > Looking forward your response. Thanx in advance. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
