Bug 15511

Summary: [965] ut2004 cause X crash when playing on the map ‘ctf-bridge of fate’
Product: Mesa Reporter: Colin.Joe <lerui.zhu>
Component: Drivers/DRI/i965Assignee: Zou Nan hai <nanhai.zou>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: medium CC: andre.nadeau, dri-devel, lerui.zhu, shuang.he
Version: git   
Hardware: Other   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: backtrace
Xorg.0.log

Description Colin.Joe 2008-04-14 19:23:42 UTC
System Environment:
--------------------------

--Platform:965
--Architecture(32-bit,64-bit,compatiblity):64bit
--2D driver:24248097988775d62f6c416f2988e74d31c91cd0
--3D driver:32134b5508495fbb1d9fc2f844e22fbb082dcda6
--DRM:db61f02bd7e4b9d5ac416f1ef98bac1bd4d984bc
--Xserver:3e12c5bb67f3049156475d5cbf4e899aaded76bb
--Kernel:2.6.25-rc3


Bug detailed description:
--------------------------
startx,type 'ut2004  ctf-bridgeoffate?spectatoronly=true?numbots=14?difficulty=7?quickstart=true?attractcam=true -windowed -benchmark -nosound -1024x768 -seconds=90 ‘
after a while , it will crash x .

 




Reproduce steps:
----------------
1. startx
2. type 'ut2004  ctf-bridgeoffate?spectatoronly=true?numbots=14?difficulty=7?quickstart=true?attractcam=true -windowed -benchmark -nosound -1024x768 -seconds=90 ‘


Current result:
----------------
X will crash .


Expected result:
----------------
run normally
Comment 1 Colin.Joe 2008-04-14 19:25:26 UTC
playing on other maps can't reproduce this bug . 
Comment 2 Colin.Joe 2008-04-14 19:27:18 UTC
Created attachment 15917 [details]
backtrace
Comment 3 Colin.Joe 2008-04-14 19:28:44 UTC
Created attachment 15918 [details]
Xorg.0.log
Comment 4 Gordon Jin 2008-04-21 01:29:30 UTC
*** Bug 15593 has been marked as a duplicate of this bug. ***
Comment 5 Zou Nan hai 2008-04-22 00:25:03 UTC
fixed in mesa
Comment 6 Adam Jackson 2009-08-24 12:29:53 UTC
Mass version move, cvs -> git

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.