[vbox-dev] VirtualBox 5.x IDisplaySourceBitmap life cycle

Rūdolfs Bundulis rudolfs.bundulis at gmail.com
Sun Jan 31 22:57:11 UTC 2016


I just had one minor follow-up question on the new VirtualBox 5.x
IFramebuffer architecture.

As part of an answer to my earlier questions this was stated:
>The returned bitmap info is valid until the next notifyChange call.

What I'd like to know is, when exactly is the memory freed? I am running
an asynchronous encoding pipeline and it would be very unlucky if the
memory of the frambuffer would be freed in a middle of a color conversion
step. The 4.x IFramebuffer interface had Lock/Unlock methods which as I
understand prevented this. Now I don't see such a mechanism any more - only
if lets say the life cycle of the video memory would be extended if I hold
a reference to the IDisplaySourceBitmap object? Does it work that way? If
no - are there any other means how I can prolong the lifetime of the buffer?

Best Regards,
Rudolfs Bundulis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.virtualbox.org/pipermail/vbox-dev/attachments/20160201/74464e6e/attachment.html 

More information about the vbox-dev mailing list