http://bugs.winehq.org/show_bug.cgi?id=26383
--- Comment #5 from Henri Verbeet hverbeet@gmail.com 2011-03-12 00:46:55 CST --- (In reply to comment #4)
trace:d3d:context_apply_fbo_state context 0x14d987b8, target 36160, render_targets 0x14dae850, depth_stencil 0x2c03c4a8, location 64 trace:d3d:context_destroy_fbo_entry context 0x14d987b8, entry 0x2ca32f00 trace:d3d:context_destroy_fbo_entry Destroy FBO 7 trace:d3d:context_destroy_fbo context 0x14d987b8, fbo 0x2ca32f18 trace:d3d:context_bind_fbo context 0x18fc48, target 36160, fbo 0x2ca32f18 trace:d3d:context_bind_fbo Binding fbo 7. trace:d3d:context_bind_fbo glBindFramebuffer() call ok context.c / 84 trace:d3d:context_clean_fbo_attachments gl_info 0x18fc48, target 36160
That's not using the FBO after it has been destroyed, actually. The "Destroy FBO 7" in context_destroy_fbo_entry() happens before the FBO is actually destroyed. The bind you see is from context_destroy_fbo(). Looking at the log, it seems to actually crash on the call to glFramebufferTexture2D() from context_clean_fbo_attachments(). That looks suspiciously like bug 21540.