Hi,
Note: I'm running version 0.9.24
I have a test app that creates a window on a layer.
Prior to IDirectFB.Release( ) I release the layer.
Then during the final IDirectFB.Release the implicit cursor window is
cleaned up - but during a dfb_windowstack_lock call it references
stack->context and at this point context has already been free'd.
I run with ElectricFence + EF_FREE_WIPES and the context is cleared to
0xbdbd...
There are two workarounds:
1/ Call DirectFBSetOption(...) with the "no-cursor" option; the test
then runs and exits with no errors as the implicit object is not created.
2/ Don't release the layer on which the windows are created and let
DirectFB cleanup these as well as the cursor; this works as DirectFB cleans
up in Windows->Layers order.
Does anyone recall this issue?
TIA,
Jason Barstow.
Notice
The information in this message is confidential and may be legally
privileged. It is intended solely for the addressee. Access to this
message by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying or distribution of the message, or
any action taken by you in reliance on it, is prohibited and may be
unlawful. If you have received this message in error, please delete it
and contact the sender immediately. Thank you.
_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
