Hi,

It could happen that the allocation's parent buffer (a CoreSurfaceBuffer)
has been released by the concurrent Fusion dispatch thread before
dfb_surfacemanager_displace() gets called (under memory pressure). As such
the associated allocation and the underlying surface manager chunk should
be accounted as free.

And happy new year!

Attachment: 0002-surfacepool-validate-allocation-buffer-before-displa.patch
Description: 0002-surfacepool-validate-allocation-buffer-before-displa.patch

Attachment: 0001-core-debugging-messages-for-the-shared-surface-pool.patch
Description: 0001-core-debugging-messages-for-the-shared-surface-pool.patch

_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to