On my windows, sometimes it show error: Cannot change thread mode after it is set about ghw HOT 7 OPEN

I think I solved this by calling hardwareID functions inside a goroutine that I lock on thread (runtime.LockOSThread)

from ghw.

it is easy to appear after calling multiple times

gpu, err := ghw.GPU()

from ghw.

@longit123 does this only happen when calling the GPU function or does this happen when you call any ghw function on Windows?

from ghw.

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

from ghw.

https://wails.io/docs/howdoesitwork/

from ghw.

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 :(

from ghw.

Please see this related thread in another project that uses WMI/go-ole:

shirou/gopsutil#692

from ghw.