Mumak wrote on 2025-05-18, 07:15:This is your opinion and you expect all others to accommodate to your design - excessive lock holding in SIV.
No this is incorrect, SIV does in general not hold locks for long at all. It used to hold the EC lock for too long on some systems when generating an EC dump, something that only usually happens when doing a save, and once I became aware of this I changed the code so it did a release/acquire at least every 4 seconds to allow for the HWiNFO timeout which was at the time 6 seconds. This change did not resolve the issue as your locking timeout design waited 3 x 2 seconds rather than 1 x 6 seconds and this caused race conditions. I recall spending time figuring out what was happening so you could fix your design.
To do all of this I needed to ask you what time timeouts HWiNFO used were and was confused as to why I was getting the HWiNFO popup after I changed SIV to do the release/acquire every 4 seconds. Once you told me it waited 3 x 2 seconds all became clear to me and I recall explaining to you what all the race conditions which which you fixed by using 1 x 6 second timeout.
Along the way I suggested simple changes to the panel that would help other developers resolve locking issues such as reporting what the HWiNFO timeout actually is and the thread name of the thread holding the lock. You eventually added the thread name, but the panel still does not report what the timeout is, I recall it's now 9 seconds, is it? Getting locking to work reliably needs us all to work together, to this end I try and make SIV provide as much information to other developers as possible.
Mumak wrote on 2025-05-18, 07:15:I never tossed dozens of screenshot on your forum blaming you to be sub-optimal and showing how great HWiNFO does in comparison to SIV. I warned you several times not to do that and especially on my forum but you won't listen. As some have probably noticed, I was avoiding to respond to your comments unless absolutely necessary to avoid feeding endless wars because of your stubbornness. But my patience is not unlimited...
I suspect we both have strong opinions and limited patience.
When I post HWiNFO + SIV screen shots I do this to show there is a solution. This is why for the dropdowns I included the SIV screen shot, should you do the same when SIV has an issue I would be quite happy with this. Much the same as I was quite happy to tell you how to query which process + thread was actually holding the lock so HWiNFO could report it when there was lock timeout.
Thinking back over most of the past 20 years, maybe longer, we all used to happily work together offline to resolve issues which was far more productive, but ever since you added the lock timeout panel I have been uncomfortable with your attitude towards cooperation. In many ways it would be easier to work together offline, it's now up to you if you wish to.
