{"comment":{"url":"https://api.github.com/repos/edx/edx-app-android/comments/12555285","html_url":"https://github.com/edx/edx-app-android/commit/c7aac64575284895463cc75280ca30f8b9fa3afb#commitcomment-12555285","id":12555285,"user":{"login":"1zaman","id":4244109,"avatar_url":"https://avatars.githubusercontent.com/u/4244109?v=3","gravatar_id":"","url":"https://api.github.com/users/1zaman","html_url":"https://github.com/1zaman","followers_url":"https://api.github.com/users/1zaman/followers","following_url":"https://api.github.com/users/1zaman/following{/other_user}","gists_url":"https://api.github.com/users/1zaman/gists{/gist_id}","starred_url":"https://api.github.com/users/1zaman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/1zaman/subscriptions","organizations_url":"https://api.github.com/users/1zaman/orgs","repos_url":"https://api.github.com/users/1zaman/repos","events_url":"https://api.github.com/users/1zaman/events{/privacy}","received_events_url":"https://api.github.com/users/1zaman/received_events","type":"User","site_admin":false},"position":31,"line":79,"path":"VideoLocker/src/main/java/org/edx/mobile/view/CourseOutlineFragment.java","commit_id":"c7aac64575284895463cc75280ca30f8b9fa3afb","created_at":"2015-08-06T01:13:20Z","updated_at":"2015-08-06T01:13:20Z","body":"@aleffert: We can set an `UncaughtExceptionHandler` on the UI thread, but I'm not sure what we can accomplish there. All the throwables caught there would either be unchecked exceptions, which are not meant to be caught even in their own scope and would be meaningless in a global scope, or errors, which are not meant to be caught in any circumstances. The only thing we might sensibly deal with would be an out of memory error, in which case we could attempt to release any memory caches that we might have, although I am not sure if we are doing anything of the sort.\r\n\r\nThe existing handler for uncaught exceptions in Android just displays a generic dialog message, while the framework restarts the thread with the previous Activity from the stack. We might be able to get rid of the error dialog with a custom handler, but I am not sure if that is a desired behaviour."}}