I somewhat doubt that quirk would help, iirc, it was added after reports
that it helped from the bringup (but by the time it got released it
didn't seem to do anything in my local testing)

0x505 is GL_OUT_OF_MEMORY, perhaps a leak?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-system-compositor in
Ubuntu.
https://bugs.launchpad.net/bugs/1654536

Title:
  unity-system-compositor crashed EGL_BAD_SURFACE

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in mir package in Ubuntu:
  New
Status in unity-system-compositor package in Ubuntu:
  New

Bug description:
  unity-system-compositor sometimes aborts on latest xenial/arm64 on
  frieza:

  $ system-image-cli -i
  current build number: 116
  device name: frieza_arm64
  channel: ubuntu-touch/staging/ubuntu
  last update: 2017-01-06 09:43:26
  version version: 116
  version ubuntu: 20170106
  version device: 20161014.0
  version custom: 20170106

  /var/log/lightdm/unity-system-compositor.log has:
  ERROR: 
/build/mir-2omL3o/mir-0.25.0+16.04.20161203/src/platforms/android/server/gl_context.cpp(233):
 Throw in function virtual void 
mir::graphics::android::FramebufferGLContext::swap_buffers() const
  Dynamic exception type: 
boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::system_error>
 >
  std::exception::what: eglSwapBuffers failure: EGL_BAD_SURFACE (0x300d)

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-system-compositor 0.8.0+16.04.20161206-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  Uname: Linux 3.10.93+ aarch64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: arm64
  Date: Fri Jan  6 10:20:54 2017
  Disassembly: => 0x7fa41dd5e8: Cannot access memory at address 0x7fa41dd5e8
  ExecutablePath: /usr/sbin/unity-system-compositor
  ExecutableTimestamp: 1480992789
  GraphicsCard:
   
  ProcCmdline: unity-system-compositor --disable-overlays=false 
--spinner=/usr/bin/unity-system-compositor-spinner --file /run/mir_socket 
--from-dm-fd 11 --to-dm-fd 14 --vt 1
  ProcCwd: /
  ProcEnviron:
   
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: unity-system-compositor
  StacktraceTop:
   ()
   std::__exception_ptr::exception_ptr::_M_release() (this=0x7fa5647b20 
<_ZN12_GLOBAL__N_121termination_exceptionE.lto_priv.2774>) at 
../../../../src/libstdc++-v3/libsupc++/eh_ptr.cc:121
   __cxa_finalize (d=0x7fa5646498) at cxa_finalize.c:56
   __do_global_dtors_aux () at /usr/lib/aarch64-linux-gnu/libmirserver.so.42
   _dl_fini () at dl-fini.c:235
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  version.libdrm: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.lightdm: lightdm 1.18.3-0ubuntu1
  version.mesa: libegl1-mesa-dev N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1654536/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to