On 10/04/12 23:44, Ezequiel Garcia wrote:
> Hello,
>
> Whenever I render from an ImageProvider to a Surface twice, without
> Flipping in between I get this warning:
>
> (!) [Main Thread 6.496] ( 737) *** Assumption [(lock)->magic !=
> D_MAGIC("CoreSurfaceBufferLock")] failed ***
> [/home/foo/DirectFB-1.4.12/source/src/core/surface_buffer.h:139 in
> dfb_surface_buffer_lock_init()]
>
> I'm using a ImageProvider cache-oriented design, instead of a Surface
> cache-oriented.
>
> Is there any danger in my procedure?
The PNG image provider for example keeps the decoded data as unscaled ARGB
in system memory once it has been rendered to a surface.
The failing assumption is interesting though, can you confirm this still
happens with latest git code?
--
Denis Oliver Kropp
DirectFB integrated media GmbH
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
