Description of problem: On my Intel-based machine, when the render window is closed, Blender crashes. Backtrace coming, waiting for debuginfo to download. Version-Release number of selected component (if applicable): blender-2.49b-1.fc12.x86_64 mesa-dri-drivers-7.6-0.13.fc12.x86_64 xorg-x11-drv-intel-2.9.1-1.fc12.x86_64 How reproducible: 100% Steps to Reproduce: 1. Render scene 2. Close render window 3. Segfault
Actually, the bt points to mesa segfault. (And it seems to work on my machine with nouveau). Reassigning to intel driver. Backtrace: #0 0x00007ffff257f414 in run_vp (ctx=0x1841980, stage=<value optimized out>) at tnl/t_vb_program.c:375 #1 0x00007ffff257cd83 in _tnl_run_pipeline (ctx=0x1841980) at tnl/t_pipeline.c:158 #2 0x00007ffff257d996 in _tnl_draw_prims (ctx=0x1841980, arrays=<value optimized out>, prim=<value optimized out>, nr_prims=<value optimized out>, ib=<value optimized out>, min_index=<value optimized out>, max_index=<value optimized out>) at tnl/t_draw.c:468 #3 0x00007ffff28f34f5 in brw_draw_prims (ctx=0x1841980, arrays=<value optimized out>, prim=0x7fffffffd350, nr_prims=1, ib=0x0, index_bounds_valid=<value optimized out>, min_index=0, max_index=3) at brw_draw.c:462 #4 0x00007ffff257518d in vbo_exec_DrawArrays (mode=6, start=0, count=<value optimized out>) at vbo/vbo_exec_array.c:523 #5 0x00007ffff25f32ac in _mesa_meta_DrawPixels (ctx=0x1841980, x=<value optimized out>, y=<value optimized out>, width=16, height=<value optimized out>, format=<value optimized out>, type=<value optimized out>, unpack=<value optimized out>, pixels=<value optimized out>) at drivers/common/meta.c:1790 #6 0x00007ffff24f5ca9 in _mesa_DrawPixels (width=16, height=16, format=6408, type=5121, pixels=0x1c5bb10) at main/drawpix.c:119 #7 0x00000000006ee39a in ?? () #8 0x000000000068e89a in ?? () #9 0x000000000069304c in ui_draw_but () #10 0x0000000000774628 in uiDrawBlock () #11 0x0000000000557e45 in scrarea_do_headdraw () #12 0x000000000055ba4e in screenmain () #13 0x0000000000553c83 in main ()
Since this bugzilla report was filed, there have been several major updates in various components of the Xorg system, which may have resolved this issue. Users who have experienced this problem are encouraged to upgrade their system to the latest version of their packages (at least F12Beta, but even better if the very latest versions). Please, if you experience this problem on the up-to-date system, let us now in the comment for this bug, or whether the upgraded system works for you. If you won't be able to reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [This is a bulk message for all open Fedora Rawhide Xorg-related bugs. I'm adding myself to the CC list for each bug, so I'll see any comments you make after this and do my best to make sure every issue gets proper attention.]
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
These bugs seem to relate to the same issue: https://bugzilla.redhat.com/show_bug.cgi?id=538394 https://bugzilla.redhat.com/show_bug.cgi?id=528372
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. [Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Running blender-2.49b-5.fc12on Fedora 12 i386 and x86_64. I can confirm this bug does not happen anymore. I can close the window by clicking the window's "x" button, re-render, close again, etc. Blender never crashes.
I don't see this happening anymore on my machine. % rpm -q blender kernel blender-2.49b-5.fc12.x86_64 kernel-2.6.31.12-174.2.3.fc12.x86_64
Thank you for letting us know.