Importing contacts trigger unity restart - Mir crashed with exception 'failed to add sync point to command buffer'

This seems to be a Mir exception:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
  what(): failed to add sync point to command buffer

which device? can a dmesg and logcat be attached? how many contacts are necessary?
This could be a system resource exhaustion issue.

This same crash happens on turbo when:

1.Open Browser app and Message app (or two apps - gallery, etc), then swipe up in Browser --Tap New tab
2.Turn your device in landscape mode
3.Swipe from right side to switch to Message app and wait a while ,maybe tap on the messages will help to reproduce

@Lorn, could you collect the logs from /system/bin/logcat and dmesg when this happens? This would help figure out if its a resource leak or some other transient driver problem that we could potentially fix or ignore.

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?

Kevin,

 I could reproduce this issue on turbo, I got your branch, and I tried to build it in docker, it took long time, and it will hang in the middle, so I can't build it successfully, now I just create a new pbuilder chroot to build it.

 How do you build the mir on armhf? Could you help provide the deb packages for testing? Thanks!

You can build for armhf on a desktop. See: doc/building_source_for_arm.md

or

http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/doc/building_source_for_arm.md

debs are at https://private-fileshare.canonical.com/~kdub/mir-debs-1554635.tar.gz. The subdirectory android-mir-1554635 contains the debs needed by the phone for the upgrade.

Also, can I see the dmesg and /system/bin/logcat logs from when the crash occurs? Seeing if the driver is logging errors to these places will help diagnose the problem.

Was able to do a bit of remote debugging with mzanetti today, latest attempt packages are here:
 https://private-fileshare.canonical.com/~kdub/mir-debs-1554635-attempt3.tar.gz

Seems the driver is failing with EGL_BAD_ALLOC when trying to install the sync point. Possibly a resource leak, or a loss of current egldisplay. The debs and updated branch will attempt to ignore the problem when it happens.

So, it seems logging the problem and not throwing is an acceptable solution, although IMO, it merits further investigation as to why the driver is generating this error during certain scenarios. Will propose attached branch to lp:mir, and its looking like it'll ride along in 0.20.3 mir release.

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.21.0

This bug was fixed in the package mir - 0.20.3+16.04.20160322-0ubuntu1

---------------
mir (0.20.3+16.04.20160322-0ubuntu1) xenial; urgency=medium

  [ Alberto Aguirre ]
  * New upstream release 0.20.3 (https://launchpad.net/mir/+milestone/0.20.3)
    - ABI summary:
      . No ABI changes in any libraries. Bugfix release only.
    - Bug fixed:
      . Mir crashed with exception 'failed to add sync point to command
        buffer' (LP: #1554635)

  [ CI Train Bot ]
  * No-change rebuild.

 -- Alberto Aguirre <email address hidden> Tue, 22 Mar 2016 15:42:36 +0000