FurMark 2.6 released

Started by JeGX, February 22, 2025, 12:48:20 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.


mirao

Hi,

benchmark works well (P2160, GL/VX). But when I click on "RUN" in the FurMark_GUI application, I'm getting this error:
----
furmark: imgui.cpp:10575: bool ImGui::ItemAdd(const ImRect&, ImGuiID, const ImRect*, ImGuiItemFlags): Assertion `id != window->ID && "Cannot have an empty ID at the root of a window. If you need an empty label, use ## and read the FAQ about how the ID Stack works!"' failed.
----

I'm running Ubuntu 24.04.2, Wayland, MSI GeForce RTX 4060 VENTUS 2X BLACK 8G OC, driver 565.77

Any idea?

JeGX

No idea, but I'll test again on linux asap. Did you use the latest version 2.6.0? 

terrance_h

#3
Same error here, neither GL nor VK works, with IG or DG

furmark: imgui.cpp:10575: bool ImGui::ItemAdd(const ImRect&, ImGuiID, const ImRect*, ImGuiItemFlags): Assertion `id != window->ID && "Cannot have an empty ID at the root of a window. If you need an empty label, use ## and read the FAQ about how the ID Stack works!"' failed.

- FurMark 2.6.0.0
- Debian, kernel 6.12.17-amd64
- X11, XFCE 4.20
- AMD 8845H with 780M + RTX4060 laptop
- NVidia driver 535.216.03-2


But another computer with Intel A770 works fine

- FurMark 2.6.0.0
- debian, kernel 6.12.12-amd64
- X11, XFCE 4.20
- Intel ARC A770
- OpenGL 4.6 , mesa 24.3.4


2.4.1.0 works well on both computers.

JeGX

Ok, I have to find the bug and fix it >:(

vinicentus

Hi!

I have the exact same problem (same output) in version 2.7.0.0 on Arch Linux.

[vincent@vincent-laptop-arch FurMark_linux64]$ ./furmark --demo furmark-gl
furmark: imgui.cpp:10575: bool ImGui::ItemAdd(const ImRect&, ImGuiID, const ImRect*, ImGuiItemFlags): Assertion `id != window->ID && "Cannot have an empty ID at the root of a window. If you need an empty label, use ## and read the FAQ about how the ID Stack works!"' failed.
Aborted (core dumped)
[vincent@vincent-laptop-arch FurMark_linux64]$ ./furmark --demo furmark-vk
furmark: imgui.cpp:10575: bool ImGui::ItemAdd(const ImRect&, ImGuiID, const ImRect*, ImGuiItemFlags): Assertion `id != window->ID && "Cannot have an empty ID at the root of a window. If you need an empty label, use ## and read the FAQ about how the ID Stack works!"' failed.
Aborted (core dumped)

Some brief system info:
I'm using wayland.
Kernel: Linux vincent-laptop-arch 6.13.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 23 Mar 2025 17:17:30 +0000 x86_64 GNU/Linux
Running mutter 48.1-1, gnome-shell 1:48.0-1, nvidia 570.133.07-2.
It's a laptop with AMD Ryzen 7 5800H with Radeon Graphics and NVIDIA GeForce RTX 3070 Laptop GPU.

JeGX

Two or three weeks ago I tried to reproduce the bug but no luck. I tested on a virtual machine (virtualbox) + latest EndeavourOS (arch linux). Maybe I have to install EndeavourOS on a real PC to see the bug... 

JeGX

[quote author=vinicentus link=msg=12297 date=1744012130]
Hi!
I have the exact same problem (same output) in version 2.7.0.0 on Arch Linux.
Do you have the bug with the GUI too?

vinicentus

Yes.

The GUI launches successfully and allows me to select the test to use. When pressing RUN, it launches a black window, that then closes, and the console outputs the same message as before. After 2 tries with different tests (gl & vk) I closed the app.

[vincent@vincent-laptop-arch FurMark_linux64]$ ./FurMark_GUI
furmark: imgui.cpp:10575: bool ImGui::ItemAdd(const ImRect&, ImGuiID, const ImRect*, ImGuiItemFlags): Assertion `id != window->ID && "Cannot have an empty ID at the root of a window. If you need an empty label, use ## and read the FAQ about how the ID Stack works!"' failed.
furmark: imgui.cpp:10575: bool ImGui::ItemAdd(const ImRect&, ImGuiID, const ImRect*, ImGuiItemFlags): Assertion `id != window->ID && "Cannot have an empty ID at the root of a window. If you need an empty label, use ## and read the FAQ about how the ID Stack works!"' failed.

[vincent@vincent-laptop-arch FurMark_linux64]$

Is there anything I can do to help further?

JeGX

Quote from: vinicentus on April 10, 2025, 11:07:39 AMYes.

The GUI launches successfully...
What I wanted to know is if the bug was also present with the GUI (no need to launch the stress test). Because the GUI and furmark share the same code.


Quote from: vinicentus on April 10, 2025, 11:07:39 AMIs there anything I can do to help further?
Yes, could you rename the GPU monitoring plugin (dylibs/plugin_gxc_gpumon_x64.so) and run the test again?

vinicentus

When renaming the lib you mentioned, the test run successfully when launched from the gui. Normal output in the cli:

[vincent@vincent-laptop-arch FurMark_linux64]$ ./FurMark_GUI
[ Demo Quick Stats ]
- demo                : FurMark (VK) (built-in: YES)
- renderer            : NVIDIA GeForce RTX 3070 Laptop GPU
- 3D API              : Vulkan 1.4.303
- resolution          : 1280x720
- frames              : 816
- duration            : 5205 ms
- FPS (min/avg/max)    : 151 / 157 / 160


[vincent@vincent-laptop-arch FurMark_linux64]$

Apologies for the late reply, I didn't get an email about your post for some reason, even though I enabeld email alerts...