SUMMARY
Severe performance issues (low FPS) in HaxBall browser game specifically on maps containing hockey floors (vector-heavy content) across multiple Linux desktop env… (leer más)
SUMMARY
Severe performance issues (low FPS) in HaxBall browser game specifically on maps containing hockey floors (vector-heavy content) across multiple Linux desktop environments and display servers. The issue is Firefox-specific, as the game performs normally on Chromium-based browsers under identical conditions.
ENVIRONMENT
Firefox Version:
- 132.0
Tested Systems and Configurations:
1) Fedora 41 KDE Plasma 6
* X11 display server
* Wayland display server
2) OpenSUSE Tumbleweed KDE Plasma 6
* X11 display server
* Wayland display server
3) Fedora 41 MATE-Compiz
* X11 display server
4) Fedora 41 Workstation (GNOME)
* X11 display server
* Wayland display server
ISSUE DESCRIPTION
• The performance degradation is consistent across all tested configurations
• Issue specifically manifests in maps with numerous vector elements (hockey floors)
• Game is virtually unplayable in vector-heavy maps
• Problem is reproducible across different desktop environments and display servers
• Performance is optimal in Chromium-based browsers under identical conditions
TEST CASE
Test Map:
The performance issues can be reproduced using this test map:
1) Map code: Available as a public Gist:
https://gist.github.com/EduMejorado/375a01d16e89fa65807ee73ef8ae1417
* Contains a hockey-type floor with vector elements that trigger the performance issue
* Can be imported directly into HaxBall for testing
* Demonstrates the performance difference between Firefox and Chromium browsers
2) Steps to reproduce:
* Download the map from the gist
* Import it into a haxball room
* Load the map in both Firefox and a Chromium-based browser
* Compare the FPS and overall performance between browsers
ATTEMPTED SOLUTIONS
The following solutions have been attempted without success:
1) Hardware Acceleration Related:
* Enabled hardware acceleration (layers.acceleration.force-enabled)
* Forced WebGL
* Run with GPU optimization flags
2) Configuration Changes:
* Enabled gfx.webrender.all
* Modified various about:config settings
3) Environment Variables:
* Tested with various Firefox flags (e.g., MOZ_ENABLE_WAYLAND=0)
4) Profile/Extensions:
* Disabled all extensions
* Created new Firefox profile
IMPACT
The performance issue makes the game unplayable specifically in Firefox, while the same content performs well in other browsers on identical systems. This suggests a Firefox-specific rendering or performance optimization issue when handling vector-heavy content.
