Let's say this. You dump the log to a file during the running and if it crashes, next time the user loads the app he/she has an option of sending the report to you. That's should be a very good option.
Ivan Soto Fernandez Web Developer http://ivansotof.com On Tue, Apr 28, 2009 at 11:26 AM, Kenn Min Chong <[email protected]> wrote: > > You should think from a user's point of view, seeing that kind of > error message for an "out of memory" issue is non specific and as > such, makes it very difficult for them to report issues to the app > creator. > > On Apr 28, 1:09 pm, Ivan Soto <[email protected]> wrote: > > The user will get a nice "This applicated failed and will now close" and > > that's why you need to debug and see the log for errors because we are > > developers. > > I don't really see the need of a more friendly way to do that. > > > > What you can also do is be writing the log to a file for later reading. > > Somebody already posted a snippet about this, search the list. > > > > Ivan Soto Fernandez > > Web Developerhttp://ivansotof.com > > > > On Tue, Apr 28, 2009 at 10:03 AM, Kenn Min Chong <[email protected]> > wrote: > > > > > > > > > Hey guys! > > > So i found the solution to debug this. Apparently ADB has a tool to > > > show the debug logs of the OS, when I did that I saw the "Out of > > > memory" error. Apparently, Android limits apps to use only 16megs of > > > memory before automatically killing it. It'd be nice though if this > > > error were shown more intuitively on the screen of the devices instead > > > of needing to find out about this via a desktop based debugger :) > > > > > On Apr 23, 1:28 pm, "Fred Grott(shareme)" <[email protected]> > > > wrote: > > > > Best bet is to post a log and than we can help you narrow it down > > > > > > On Apr 22, 7:03 pm, Kenn Min Chong <[email protected]> wrote: > > > > > > > Hi there! > > > > > For some reason I can't explain, when my app runs, I will on > > > > > occasion get the following error message: > > > > > > > “The application xxxxxxxx (process xxxxxx) has stopped > unexpectedly. > > > > > Please try again.” > > > > > > > When I debug my code, it seems to break at random places that > doesn't > > > > > make sense. On top of that I tried to surround the entire code with > a > > > > > try/catch block just to try to catch the exception, but it doesn't > > > > > work either. I'm suspecting it's the OS that is producing this > error > > > > > message but I don't know why. As far as my code goes, if there were > > > > > exceptions caused by it, it would've been caught by the try/catch > > > > > block. Can someone shed some light here? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
