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):
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
A "Segmentation fault" occurs.
Either the benchmark or the game should have started.
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.
Thanks for the bug report and the patch! I'm preparing an updated version of glaxium incorporating your fix now.
glaxium-0.5-13.fc16 has been submitted as an update for Fedora 16.
glaxium-0.5-13.fc17 has been submitted as an update for Fedora 17.
* 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:
then log in and leave karma (feedback).
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.
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.