unity8 crash with many random touch points

[Michael Zanetti]

I've just put my flat hand onto arale's screen and unity8 crashed. Turns out I could reproduce this quite easily and managed to capture a trace: http://paste.ubuntu.com/11113929/

[Daniel d'Andrada (dandrader)]

Could be a duplicate of bug #1437357

[Michael Zanetti (mzanetti)]

Unlikely it's a dupe.

The fix for bug #1437357 was released to revision 0.4.4+15.04.20150511.1-0ubuntu1. I do have that one installed.

[Daniel d'Andrada (dandrader)]

This is what I got in unity8.log after tapping like crazy, causing unity8 to crash:

"""
qtmir.surfaces: MirSurfaceItem::setOrientation - orientation= 2
qtmir.surfaces: MirSurfaceItem::updateMirSurfaceFocus true
qtmir.clipboard: D-Bus GetContents - returning 0 bytes
qtmir.mir.input: Would move a touch that wasn't pressed before (id = 15 ). Making it press instead.
qtmir.mir.input: There's a touch (id = 14 ) missing. Releasing it.
qtmir.mir.input: There's a touch (id = 20 ) missing. Releasing it.
qtmir.mir.input: There's a touch (id = 26 ) missing. Releasing it.
qtmir.mir.input: There's a touch (id = 33 ) missing. Releasing it.
qtmir.mir.input: Would move a touch that wasn't pressed before (id = 36 ). Making it press instead.
qtmir.mir.input: There's a touch (id = 35 ) missing. Releasing it.
terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::logic_error> >'
  what(): Only one touch up/down may be reported per event
"""

So it's the same as bug #1437357, as I suspected. Which means that my fix for it didn't work or didn't cover all cases :-/