Bug 2733 - Blender crashes after using renderer for more than 2 times with i810
Summary: Blender crashes after using renderer for more than 2 times with i810
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Demos (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
URL: http://projects.blender.org/tracker/?...
Whiteboard:
Keywords:
: 3076 4317 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-03-15 01:09 UTC by Slavej Karadjov
Modified: 2005-10-18 21:35 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Slavej Karadjov 2005-03-15 01:09:47 UTC
The following problem is easy to reproduce.
My OS is Slackware Linux 10.1.
The problem happens with compiled dynamic version from the site and with the
CVS version compiled on my OS. 
I'am using: X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2

Start blender. Render scene. Close the render window. Try to render again. New
render window will appear. Close it again. Press f12 and.. blender will crash
with seg fault.

Below is the input from gdb

slavej@slavej:~/cvs/blender$ gdb blender
GNU gdb 6.3
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-slackware-linux"...Using host libthread_db
library "/lib/libthread_db.so.1".

(gdb) start
Breakpoint 1 at 0x80eb0f6
Starting program: /home/slavej/cvs/blender/blender
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 7934)]
[Switching to Thread 16384 (LWP 7934)]
0x080eb0f6 in main ()
(gdb) continue
Continuing.


Program received signal SIGFPE, Arithmetic exception.
0x4073680c in _mesa_test_os_sse_exception_support () from
/usr/X11R6/lib/modules/dri/i810_dri.so
(gdb) continue
Continuing.

>>> Here is the moment that I repeat the steps explained above. The scene
contains ONLY the default cube.

Program received signal SIGSEGV, Segmentation fault.
0x4073f119 in __driGarbageCollectDrawables () from
/usr/X11R6/lib/modules/dri/i810_dri.so

(gdb) backtrace
#0 0x4073f119 in __driGarbageCollectDrawables () from
/usr/X11R6/lib/modules/dri/i810_dri.so
#1 0x4073fe4a in driCreateNewContext () from /usr/X11R6/lib/modules/dri/i810_dri.so
#2 0x402841be in DriverCreateContextWrapper () from /usr/X11R6/lib/libGL.so.1
#3 0x402846bf in CreateContext () from /usr/X11R6/lib/libGL.so.1
#4 0x402849be in glXCreateContext () from /usr/X11R6/lib/libGL.so.1
#5 0x08341d45 in GHOST_WindowX11::installDrawingContext ()
#6 0x083410b1 in GHOST_WindowX11::GHOST_WindowX11 ()
#7 0x0833f5e9 in GHOST_SystemX11::createWindow ()
#8 0x0833e289 in GHOST_CreateWindow ()
#9 0x08129d59 in window_open ()
#10 0x08170cd1 in open_renderwin ()
#11 0x08170ffd in renderwin_init_display_cb ()
#12 0x08171970 in do_render ()
#13 0x08171c85 in BIF_do_render ()
#14 0x08138493 in do_info_rendermenu ()
#15 0x0815596a in uiDoBlocks ()
#16 0x08119f2f in scrarea_dispatch_header_events ()
#17 0x0811ae6e in screen_dispatch_events ()
#18 0x0811b1b5 in screenmain ()
#19 0x080eb2bf in main ()
Comment 1 Alan Hourihane 2005-03-15 02:40:34 UTC
It's a known bug in the DRI common code. It's been fixed, so you might want to
try the CVS to see if it solves your problem.
Comment 2 Slavej Karadjov 2005-03-17 01:59:18 UTC
(In reply to comment #1)
> It's a known bug in the DRI common code. It's been fixed, so you might want to
> try the CVS to see if it solves your problem.

Which CVS and modules I have to check out and compile? I am asking this because
there is mesa and drm CVS with modules.

Comment 3 Adam Jackson 2005-10-19 14:33:35 UTC
*** Bug 4317 has been marked as a duplicate of this bug. ***
Comment 4 Adam Jackson 2005-10-19 14:33:45 UTC
*** Bug 3076 has been marked as a duplicate of this bug. ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.