Bug 815826

Summary: glaxium will sometimes crash when doing a benchmark or simply playing
Product: [Fedora] Fedora Reporter: Hans Otten <bobbel42>
Component: glaxiumAssignee: Hans de Goede <hdegoede>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: hdegoede
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: glaxium-0.5-13.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-04 22:56:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
A patch for this bug none

Description Hans Otten 2012-04-24 15:36:57 UTC 
Description of problem:
glaxium will sometimes crash when doing a benchmark or simply playing. The crash is due to a segmentation violation.

Version-Release number of selected component (if applicable):
0.5-10.fc16

How reproducible:
always (on my 2 systems with NVidia based graphic cards)

Steps to Reproduce:
1. start glaxium
2. press F3 to start the benchmark or press space to play the game
3.
  
Actual results:
A "Segmentation fault" occurs.

Expected results:
Either the benchmark or the game should have started.

Additional info:
Comment 1 Hans Otten 2012-04-24 15:47:25 UTC 
Created attachment 579897 [details]
A patch for this bug

The root cause of the bug turned out to be an index out of bounds access to the fighter2_meshes array in fighter2.cpp. Although there are only 578 faces in the array the loop starting at fighter2.cpp:90 tries to run through 587 faces. See also the file "modeles/fighter2.c".

An even better patch would make all this depend on the size of the fighter2_meshes array itself.
Comment 2 Hans de Goede 2012-05-03 08:00:06 UTC 
Thanks for the bug report and the patch! I'm preparing an updated version of glaxium incorporating your fix now.
Comment 3 Fedora Update System 2012-05-03 08:31:59 UTC 
glaxium-0.5-13.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/glaxium-0.5-13.fc16
Comment 4 Fedora Update System 2012-05-03 08:32:26 UTC 
glaxium-0.5-13.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/glaxium-0.5-13.fc17
Comment 5 Fedora Update System 2012-05-03 16:01:03 UTC 
Package glaxium-0.5-13.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing glaxium-0.5-13.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-7213/glaxium-0.5-13.fc17
then log in and leave karma (feedback).
Comment 6 Fedora Update System 2012-05-04 22:56:28 UTC 
glaxium-0.5-13.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 7 Fedora Update System 2012-05-13 01:59:20 UTC 
glaxium-0.5-13.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.