Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial


App crashes when hourly button is clicked.

This is the message in the logs: 06-21 08:23:59.956 1028-1094/system_process E/InputDispatcher: channel '10db867e com.example.x.raid/com.example.x.raid.ui.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed! 06-21 08:23:59.958 1028-2565/system_process I/WindowState: WIN DEATH: Window{10db867e u0 com.example.x.raid/com.example.x.raid.ui.MainActivity} 06-21 08:23:59.958 1028-2565/system_process W/InputDispatcher: Attempted to unregister already unregistered input channel '10db867e com.example.x.raid/com.example.x.raid.ui.MainActivity (server)'

This is the project: https://github.com/Max-Mudu/Raid

All help will be highly appreciated. Thanks.

2 Answers

Hi Farah,

Last time I saw this error, we didn't really get to the bottom of it. Have a read here.

I'll reiterate my advice on the above thread; try the memory monitor to see if the app loads memory massively. That can cause the target to be removed, which is what causes the 'unrecoverably broken' exit message.

It's great you have a GitHub repo - that really helps. Keep it right up to date. I'll pull it down now but I can't guarantee to spend any time on it tonight. It's 9:30pm now and I've been troubleshooting code in multiple languages all week. I need a night off as my brain is fried.

I'll look over the weekend, though, if I get chance.

If you make changes to the repo, let me know in here. I'll push changes to you if I make any.


Thanks Steve, from the look of things from the memory monitor, I am not sure how to read it but there is a slight rise in memory when the the crash occurs and then a sharp drop which remains constant. And don't worry about it, just do it whenever you can and let me know of any changes. I will do the same. thanks