@Timster
Many thanks for the video!!
WRT follows "% Commited Bytes in Use" from Performance Monitor, that, from what I gathered, takes into account the pagefile size, hence the difference to the values displayed in the task manager - from what I tested, this difference will really standout when the memory use is very high; when the use is not that high the values are close. I'll try to find another way to get the used memory. Thanks a lot for reporting and help with the troubleshoot!
Meanwhile I’ve released version 1.9.1.0 of WRT.
This version fixes an unhandled exception that would crash the program during its startup if the CPU wasn’t supported by the temperature monitor. A few other unhandled exceptions that might also occur during the startup were also handled. This problem affected versions 1.9.0.7 and higher.
Thanks to the user Scott T. for reporting the issue.
Many thanks for the video!!
WRT follows "% Commited Bytes in Use" from Performance Monitor, that, from what I gathered, takes into account the pagefile size, hence the difference to the values displayed in the task manager - from what I tested, this difference will really standout when the memory use is very high; when the use is not that high the values are close. I'll try to find another way to get the used memory. Thanks a lot for reporting and help with the troubleshoot!
Meanwhile I’ve released version 1.9.1.0 of WRT.
This version fixes an unhandled exception that would crash the program during its startup if the CPU wasn’t supported by the temperature monitor. A few other unhandled exceptions that might also occur during the startup were also handled. This problem affected versions 1.9.0.7 and higher.
Thanks to the user Scott T. for reporting the issue.