Thanks for the idea Ben but the application doesn't have any explicit finalizers. The few that are used in referenced libraries shouldn't be able to generate an error and if they did, I would have expected to see this behaviour in other apps since they are used in every other app we have. Having said that, maybe I should put some try/catches in them anyway.
It's a .netcf 2 app running on WM 6.1. David "If we can hit that bullseye, the rest of the dominoes will fall like a house of cards... checkmate!" -Zapp Brannigan, Futurama On Thu, Aug 4, 2011 at 13:54, <[email protected]> wrote: > ** > I don't know if its a .NET application, but if it is then you should have a > look at all your finalizers. Any unhandled exception in a finalizer will > cause your application to disappear without warning or any chance to catch > or recover (since this is happening on the GC's thread, not your app there > isn't much else the runtime can do). I've seen the symptoms you describe a > couple of times and both times an unhandled exception in the finalizer was > the cause. > > Cheers, > Ben > >
