HACK - Avoid crashes on SurfaceFlinger when using software rendering
When using sw rendering, depending user action (pressing HOME button after
lauching an app, for instance) there's an attempt do map a vaddr that has
already been mapped. And this is done by the process that created it.
This triggers a kernel trap and surfaceflinger is destroyed:
=========================================================================
10-30 18:14:11.474 1096 1645 D gralloc : gralloc_map() succeeded fd=59,
off=0, size=
1028096, vaddr=0xaac21000
10-30 18:14:11.474 1355 1389 D gralloc : gralloc_map() succeeded fd=202,
off=0, size=
1028096, vaddr=0x8d0f2000
10-30 18:14:11.475 1096 1096 D gralloc : Registering a buffer in the
process that created it. This may cause memory ordering problems.
10-30 18:14:11.475 1096 1096 D gralloc : gralloc_map() succeeded
fd=60, off=0, size=
1028096, vaddr=0xaac21000
10-30 18:14:11.574 1095 1095 I ServiceManager: service 'gpu' died
=========================================================================
In order to avoid this, the patch avoids mapping a buffer when the
mapping process is the creator process.
This should be threated as a workaround and removed when the real
root cause is discovered.
OSDN Git Service
