Comment 8 for bug 1554635

Attached a branch that will at least ignore the exception. Without being able to reproduce myself (mir team doesn't have a turbo) or without seeing dmesg and logcat, its hard to tell if masking the exception is an appropriate response. Best guess though with information at this point in time is that its a transient problem that can be ignored.

Could someone who can reproduce the problem try with the attached branch?