Open longit123 opened 1 year ago
it is easy to appear after calling multiple times
gpu, err := ghw.GPU()
@longit123 does this only happen when calling the GPU
function or does this happen when you call any ghw
function on Windows?
I am using wails + front-end development. Wails will monitor file updates during development and then perform hot updates. When I did not use ghw before, this problem did not occur. After using ghw, this problem will appear. After I Googled it, it may be due to the use of wails webview2, caused by hot update, I don't know how to solve this problem
ghw
does not write any files so I don't believe the file monitoring that Wails (or Vite) does is part of this. I suspect this may be a problem with the go-ole/go-ole
library that the StackExchange/wmi
dependency uses. Unfortunately, I don't know if there's anything that ghw
can do to address this issue :(
Please see this related thread in another project that uses WMI/go-ole:
I think I solved this by calling hardwareID functions inside a goroutine that I lock on thread (runtime.LockOSThread)
ghw version: v0.10.0 GPU: RTX3070 Win10: 21H2 19044.1889 Go version: 1.19.6