Just saw @Yochanan updated the hardinfo-git AUR build (“ignore odr-violation errors”).
I do get those violations when starting hardinfo as root, however.
(Memory info is incorrect, related to this issue, I think.)
Just saw @Yochanan updated the hardinfo-git AUR build (“ignore odr-violation errors”).
I do get those violations when starting hardinfo as root, however.
(Memory info is incorrect, related to this issue, I think.)
The program fails to run properly without using ASAN_OPTIONS=detect_odr_violation=0
, so I added it to the menu shortcut. Run hardinfo
from the terminal to see what I mean. Then run ASAN_OPTIONS=detect_odr_violation=0 hardinfo
to run the program and see the output.
There’s a huge memory leak currently. I ran it for a few minutes clicking around and it went up to ~ 450 MB.
SUMMARY: AddressSanitizer: 405251 byte(s) leaked in 11471 allocation(s).
Hmm, can’t reproduce it. It shows the correct value for me.
Running it as sudo ASAN_OPTIONS=detect_odr_violation=0 hardinfo
displays it correctly. I can’t remember if I needed admin priviledges for correct memory information previously (“Memory Devices” says it needs dmidecode and admin privileges, or at24/ee1004, which I’m not familiar with…).
Thanks for the update!
“Memory Devices” says it needs dmidecode
Oh right, forgot to add that to optional dependencies. Just pushed an update that should have all of them.