Hello Devs, I wanted to create some scripted/automated benchmark, but seems like the visible(correctly generated) data won't save into the dump files, however they were created. I used the following command: GALLIUM_HUD_DUMP_DIR="/media/ramdisk/" GALLIUM_HUD="fps,cpu" /usr/share/playonlinux/playonlinux --run "LFS" The ownerships are fine glxgears were able to generate data, but it depends on the exitcode as I experienced. I'm using rolling Arch with: linux 4.10.11-1 mesa 17.0.4-2 wine-gaming-nine 2.3-1 xorg-server 1.19.3-2 It's working if I disable the Gallium nine in the settings. Thank you
There is a patch in git master that maybe helps: https://cgit.freedesktop.org/mesa/mesa/commit/?id=5589fd89e1337a03c947840b344f515cb1d3a96d Just to be sure: Are you seeing empty fps and cpu files in /media/ramdisk/ or the files don't get created at all?
Yes the files are exist, but there is no data.
The current patch is sending the data line-by-line instead of sending the whole output at the exit. Right? Maybe the exit status won't affect the data generation.
The original code in 17.0 should just flush the I/O buffer to the file when the buffer size reaches the default BUFSIZ value (8 KB on my machine) or when fclose is called. You usually have to wait longer to see something in the files. I'm not sure why with some applications the fclose doesn't get called on exit. With the new patch the I/O buffer gets flushed after every printf with newline. This is probably the expected behavior and it doesn't seem to negatively impact the performance. Release 17.1 is expected for end next week and the patch is included.
Hi Balázs Did you have a chance to check mesa 17.1 if the problem is solved for you? Thanks edmondo
Sorry for the late answer. Yes, it's fine.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.