On Tue, Feb 3, 2009 at 7:11 PM, Marcus von Appen <[email protected]> wrote: > On, Tue Feb 03, 2009, Lenard Lindstrom wrote: [cut] >> Well, for starters the buffer proxy object only borrows a reference to >> its parent surface (no PY_INCREF/PY_DECREF calls). > > Which should be absolutely okay, as surface.get_buffer() acquires a > lock. >
hrmm... I think it could matter if the parent surface gets to reference count 0 -- when the buffer still exists, and then the surface tries to deallocate the parent surface memory... thus making the buffer point to invalid memory. ?
