Thanks for your quick response. It doesn't access or modify any views. It accesses the context to read in some raw resources and writes to the sqllite database also via context.
On Mar 13, 9:32 am, Streets Of Boston <flyingdutc...@gmail.com> wrote: > Hi Bob, > > Your code snippet is not enough to give you some more info. > E.g. how does backgroundRefresh2 looks like (it public void run() > implementation). > > Based on its name 'backgroundRefresh2': does it access View-s and > modify these view (e.g. update text-view, images, etc.)? > If so, that may explain your crash. You should not access any View (or > subclass of View) in any other thread than your main message- > dispatching thread (i.e. the thread on which your onCreate/onDestroy/ > onPause/onResume/on<anything> is called). > > On Mar 13, 11:05 am, Bob <bshumsk...@yahoo.com> wrote: > > > Hi, > > I have moved some intensive processing from my main thread to a > > service. My UI is hanging and then crashing when I start the service, > > even if I put the service start in a new thread started via > > > Thread updateThread = new Thread(null, backgroundRefresh2, > > "new_thread"); > > updateThread.start(); > > > What am I doing wrong? Also, it seems like the cause of the eventual > > crash in the service/worker thread doesn't show up in LogCat. > > > Thanks, > > Bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
