(If US-English language pack is activated everything works, except 'Total VRAM Usage').
Mind turning on debug logging (Under manage > settings and clicking the checkbox in about > log) and posting the results so that way I can see if it is a language issue?
Last edited by tjhrulz on May 11th, 2018, 8:52 pm, edited 1 time in total.
- Here's the log you asked for (only a few cycles):
ved UsageMonitor.Categories.Counters.UpdateCategory(String category)
DBUG (20:50:18.461) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:18.587) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core0Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:18.619) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core1Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:19.434) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [MeasureBrowser]: Could not find a counter in category Processor called % Processortid
ERRO (20:50:19.438) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: UsageMonitor crashed trying to update the counterss
DBUG (20:50:19.438) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Det blev forsøgt at læse eller skrive i en beskyttet hukommelse. Dette kan ofte være et tegn på, at en anden hukommelse er beskadiget.
DBUG (20:50:19.438) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: ved Rainmeter.API.RmLog(IntPtr rm, LogType type, String message)
ved UsageMonitor.Categories.Counters.UpdateCategory(String category)
DBUG (20:50:19.476) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:19.616) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core0Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:19.647) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core1Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:20.437) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [MeasureBrowser]: Could not find a counter in category Processor called % Processortid
ERRO (20:50:20.441) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: UsageMonitor crashed trying to update the counterss
DBUG (20:50:20.441) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Det blev forsøgt at læse eller skrive i en beskyttet hukommelse. Dette kan ofte være et tegn på, at en anden hukommelse er beskadiget.
DBUG (20:50:20.441) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: ved Rainmeter.API.RmLog(IntPtr rm, LogType type, String message)
ved UsageMonitor.Categories.Counters.UpdateCategory(String category)
DBUG (20:50:20.478) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:20.603) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core0Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:20.635) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core1Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:21.452) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [MeasureBrowser]: Could not find a counter in category Processor called % Processortid
ERRO (20:50:21.486) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: UsageMonitor crashed trying to update the counterss
DBUG (20:50:21.486) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Det blev forsøgt at læse eller skrive i en beskyttet hukommelse. Dette kan ofte være et tegn på, at en anden hukommelse er beskadiget.
DBUG (20:50:21.486) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: ved Rainmeter.API.RmLog(IntPtr rm, LogType type, String message)
About the VRAM-measure: I can't make it work even if I use PerfMon, so maybe that's a problem occuring only on my computer? (a Rainmeter-restart as you suggest doesn't help either).
Stone wrote:- Here's the log you asked for (only a few cycles):
ved UsageMonitor.Categories.Counters.UpdateCategory(String category)
DBUG (20:50:18.461) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:18.587) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core0Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:18.619) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core1Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:19.434) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [MeasureBrowser]: Could not find a counter in category Processor called % Processortid
ERRO (20:50:19.438) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: UsageMonitor crashed trying to update the counterss
DBUG (20:50:19.438) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Det blev forsøgt at læse eller skrive i en beskyttet hukommelse. Dette kan ofte være et tegn på, at en anden hukommelse er beskadiget.
DBUG (20:50:19.438) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: ved Rainmeter.API.RmLog(IntPtr rm, LogType type, String message)
ved UsageMonitor.Categories.Counters.UpdateCategory(String category)
DBUG (20:50:19.476) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:19.616) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core0Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:19.647) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core1Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:20.437) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [MeasureBrowser]: Could not find a counter in category Processor called % Processortid
ERRO (20:50:20.441) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: UsageMonitor crashed trying to update the counterss
DBUG (20:50:20.441) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Det blev forsøgt at læse eller skrive i en beskyttet hukommelse. Dette kan ofte være et tegn på, at en anden hukommelse er beskadiget.
DBUG (20:50:20.441) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: ved Rainmeter.API.RmLog(IntPtr rm, LogType type, String message)
ved UsageMonitor.Categories.Counters.UpdateCategory(String category)
DBUG (20:50:20.478) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:20.603) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core0Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:20.635) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [Core1Usage]: Could not find a counter in category Processor called % Processortid
DBUG (20:50:21.452) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [MeasureBrowser]: Could not find a counter in category Processor called % Processortid
ERRO (20:50:21.486) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: UsageMonitor crashed trying to update the counterss
DBUG (20:50:21.486) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: Det blev forsøgt at læse eller skrive i en beskyttet hukommelse. Dette kan ofte være et tegn på, at en anden hukommelse er beskadiget.
DBUG (20:50:21.486) UsageMonitorExamples\BasicExampleWin10\BasicExample.ini - [TotalVRAM]: ved Rainmeter.API.RmLog(IntPtr rm, LogType type, String message)
About the VRAM-measure: I can't make it work even if I use PerfMon, so maybe that's a problem occuring only on my computer? (a Rainmeter-restart as you suggest doesn't help either).
Somehow you triggered a memory corruption error, that is a new one. Also somehow your TotalVRAM usage is referencing the wrong counter and category. I think I have an idea though on the cause for this though.
To all of you with issues please try the just released Rainmeter 4.2 Beta Release - r3101. With any luck this should stop the one remaining crash and fix any language issues. This Includes preventing custom categories/counters in your native language from having issues, Although I still recommend translating them into english so they work with all languages. In the future I plan on having a debug log alert you to the english translation of the category/counter
tjhrulz wrote:To all of you with issues please try the just released Rainmeter 4.2 Beta Release - r3101. With any luck this should stop the one remaining crash and fix any language issues.
Perfect using r3104 with french OS.
Here is a skin test (GPU doesn't work because my Windows is still v1607)