Note that the crash is fixed in 1.6 by http://bazaar.launchpad.net/~oxide-developers/oxide/1.6/revision/944 - in this case, Oxide will run in software compositing mode.
Marking 1.6 as Won't Fix, as the change in http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/1025 won't change that behaviour. This is because the mirserver QPA plugin doesn't allow Oxide to access the platform handle for the share context if one is provided (see https://code.launchpad.net/~mterry/oxide/mirserver/+merge/255128/comments/634515), which is required for GPU compositing.
On trunk (1.7), Michael's change enables Oxide to use the EGLImage compositing path, but that doesn't exist in 1.6 (it requires http://bazaar.launchpad.net/~oxide-developers/oxide/oxide.trunk/revision/1017).
Note that the crash is fixed in 1.6 by http:// bazaar. launchpad. net/~oxide- developers/ oxide/1. 6/revision/ 944 - in this case, Oxide will run in software compositing mode.
Marking 1.6 as Won't Fix, as the change in http:// bazaar. launchpad. net/~oxide- developers/ oxide/oxide. trunk/revision/ 1025 won't change that behaviour. This is because the mirserver QPA plugin doesn't allow Oxide to access the platform handle for the share context if one is provided (see https:/ /code.launchpad .net/~mterry/ oxide/mirserver /+merge/ 255128/ comments/ 634515), which is required for GPU compositing.
On trunk (1.7), Michael's change enables Oxide to use the EGLImage compositing path, but that doesn't exist in 1.6 (it requires http:// bazaar. launchpad. net/~oxide- developers/ oxide/oxide. trunk/revision/ 1017).