Package Details: furmark 2.10.2-1

Git Clone URL: https://aur.archlinux.org/furmark.git (read-only, click to copy)
Package Base: furmark
Description: Lightweight but intensive GPU stress test and benchmarking tool for OpenGL and Vulkan
Upstream URL: https://www.geeks3d.com/furmark/v2/
Licenses: custom:freeware
Submitter: alou-S
Maintainer: vinicentus
Last Packager: vinicentus
Votes: 11
Popularity: 0.62
First Submitted: 2024-01-18 08:27 (UTC)
Last Updated: 2025-10-28 09:38 (UTC)

Dependencies (6)

Required by (0)

Sources (4)

Latest Comments

1 2 Next › Last »

dreieck commented on 2026-01-30 23:58 (UTC)

Xft.dpi: 96 in ~/.Xresources seems also to be needed to avoid segmentation faults if native X.Org is used (no Wayland) and display DPI is already at 96 DPI.

dreieck commented on 2026-01-30 23:28 (UTC)

Ahoj,

this package uses precompiled binaries.

So you must rename it to furmark-bin, and then add provides=("furmark=${pkgver}"), conflicts=("furmark"), replaces=("furmark<=2.10.2").

Regards and thank you for this package!

spk44 commented on 2026-01-07 04:24 (UTC) (edited on 2026-01-07 04:25 (UTC) by spk44)

For those who are experiencing segfaults on Wayland, you can add

Xft.dpi: 96

to the ~/.Xresources file, then run

xrdb -merge ~/.Xresources

From the xorg-xrdb package to solve the segfault

nardis commented on 2025-09-16 16:05 (UTC) (edited on 2025-09-16 17:37 (UTC) by nardis)

@vinicentus thanks for reporting. I'll take a closer look now that there's confirmation that it actually works for somebody.

Edit: I seem to experience the same issue to this forum post: https://www.geeks3d.com/forums/index.php/topic,8202.0.html. At least my stack trace is similar: some X11 DPI related issue on a Wayland (SwayWM) system with either gfx1036 APU (AMD Raphael) or gfx1100 GPU (AMD RX9700XT):

Stack trace of thread 30392:
#0  0x00007f6fc5da289c n/a (libc.so.6 + 0x1a289c)
#1  0x00007f6fc64e9543 n/a (libX11.so.6 + 0x48543)
#2  0x00007f6fc64ee9ba XrmGetStringDatabase (libX11.so.6 + 0x4d9ba)
#3  0x0000000000439ff0 _Z17X11_GetMonitorDPIP9_XDisplay (/opt/furmark/FurMark_GUI + 0x39ff0)
#4  0x00007f6fc7848bdd _Z24gxl_utils_get_system_dpiPi (libgxl_r_linux_x64.so + 0x248bdd)
#5  0x000000000041dacd n/a (/opt/furmark/FurMark_GUI + 0x1dacd)
#6  0x000000000042166a n/a (/opt/furmark/FurMark_GUI + 0x2166a)
#7  0x0000000000420e9f n/a (/opt/furmark/FurMark_GUI + 0x20e9f)
#8  0x00000000004246d2 n/a (/opt/furmark/FurMark_GUI + 0x246d2)
#9  0x00000000004249c5 n/a (/opt/furmark/FurMark_GUI + 0x249c5)
#10 0x00000000004242b2 n/a (/opt/furmark/FurMark_GUI + 0x242b2)
#11 0x0000000000429ece n/a (/opt/furmark/FurMark_GUI + 0x29ece)
#12 0x000000000042521c n/a (/opt/furmark/FurMark_GUI + 0x2521c)
#13 0x00007f6fc5c27b0b n/a (libc.so.6 + 0x27b0b)
#14 0x00007f6fc5c27bbb __libc_start_main (libc.so.6 + 0x27bbb)
#15 0x000000000041785a n/a (/opt/furmark/FurMark_GUI + 0x1785a)
ELF object binary architecture: AMD x86-64

I tried running it in gamescope, but no luck. Eh, it's whatever.

vinicentus commented on 2025-09-12 07:22 (UTC)

@nardis It works for me on nvidia dgpu and amd igpu, maybe try understanding why it crashes?

nardis commented on 2025-09-04 13:03 (UTC)

Does this work for anyone at all? No matter what I do, the app crashes with an "terminated by signal SIGSEGV (Address boundary error)" when trying to run any demo or the GUI. For both, this AUR package and original 7z archive.

vinicentus commented on 2025-05-21 08:21 (UTC)

Thanks, I'll update this next week.

alou-S commented on 2025-05-19 12:20 (UTC)

I have transferred the maintainership of the package over to @vinicentus

1 2 Next › Last »