When I stop TeamRedMiner via Awesome Miner, the console window of TeamRedMiner says "Shutting down..." and then it will exit right away. Don't you get any console message at all?
Awesome Miner do have a behavior to kill the mining process if it didn't resond to the first request to shutdown. Maybe you can increase the time Awesome Miner will wait to see if TeamRedMiner just needed a bit more time to close down in a nice manner? Increase the value of: Options -> Mining Settings -> Wait for process before terminating.
Thanks for describing the case about dev fee as well. Awesome Miner doesn't have any feature today to do this on a mining software basis. Some mining software also have different dev fee depending on algorithm.
Yeah in my case, awesome miner does an insta-kill, i tried the timeout but no avail.
I tried closing TRM with a ctrl+c, works normally, the thread shudown and miner closes
I'm not able to reproduce the problem - although I do see that TeamRedMiner terminate very fast, it says "Shutting down" for a very show moment before doing so. Not easy to see that message because the process is so fast.
The fact that TeamRedMiner terminates very fast in your case as welll indicates that it did respond to the friendly Window close message from Awesome Miner. If it didn't respond, the close process would have taken about 5 seconds (configurable) before Awesome Miner took the next action where the process is killed.
To compare with SrbMiner, it says "Releasing GPU resources", but it takes 2 seconds so it's easier to see that message.
Awesome Miner is first sending a friendly request to close the mining window to the mining software - and this is the same for all mining software. You can try the same behavior by closing the mining software with the X-button in the mining window. When you click X to close the window, it should be the same concept as when Awesome Miner requests to close the mining window. When I try this with TeamRedMiner and SrbMiner, I do get the exact same behavior as when Awesome Miner do it. Could you compare with this as well?
I tried logging the exit process, and confirm that the TRM isnt shutting down normally.
TRM shutdown works only with Ctrl+C and not when clicking close in the CMD windows.
Feature Request : Allow Total miner power usage value as a property in the status object.
https://support.awesomeminer.com/support/solutions/articles/35000086023-customize-progress-fieldTrying to bring this value to Progess Field
"Efficiency: " + Math.Round(status.KHashAvg / {{{status.PowerUsage}}}, 2) +" KHash/Watt"Thanks !!
I think this is a TRM issue about not being consistent in how it closes down when using the X-button. I do get a close down message on my system when I do this - while you don't.
It's quite easy to expose the power usage so I can do that in one of the next versions. You can expect the following to work once available:
status.KHashAvg * 1000 / Math.Max(miningHelper.GetPowerUsage(), 1), 2)
As the Power Usage might be 0 in the very beginning, using the Math.Max operation will ensure that we never go below '1' in assumed power usage.
When you press (X) you trigger a CTRL_CLOSE signal rather than CTRL_BREAK or CTRL_C. This one is a little special under Windows, it will send the signal to all processes connected to the console, then also proceed to kill the process(es) after some timeout.
Only 95% sure about this, but I after a quick test it seems Windows actually proceeds to kill the process after the signal handler(s) for all processes has returned, not after a timeout. We have an async shutdown procedure, i.e. the signal handler just sets a flag and triggers a cond var, then returns, and other threads in the process take care of the shutdown. Unfortunately, Windows kills the process before those threads even have gotten started. Sometimes you'll see the first log message, other times you don't. We need to add a block in the Windows signal handler and don't return before the shutdown has completed, or you can send CTRL_BREAK/CTRL_C or char input 'q' to the process, all those fixes should have the effect of a proper shutdown taking place.
-- K
