(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?
Re: Need some language testing for UsageMontitor
Posted: May 10th, 2018, 6:56 pm
by Stone
- 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).
Re: Need some language testing for UsageMontitor
Posted: May 11th, 2018, 8:59 pm
by tjhrulz
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.
NOTE (02:03:51.719) test\UsageMonitor plugin.ini: Refreshing skin
DBUG (02:03:51.724) : Reading file: D:\Programmes\Customisation\Rainmeter\Rainmeter.ini
DBUG (02:03:51.729) test\UsageMonitor plugin.ini: Reading file: D:\Programmes\Customisation\Rainmeter\Skins\test\UsageMonitor plugin.ini
ERRO (02:03:53.058) : UsageMonitor crashed trying to update the counters
DBUG (02:03:53.063) : L'élément a déjà été ajouté. Clé du dictionnaire : 'taille virtuelle (octets)' Clé ajoutée : 'taille virtuelle (octets)'
DBUG (02:03:53.070) : à System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
à System.Collections.DictionaryBase.System.Collections.IDictionary.Add(Object key, Object value)
à System.Diagnostics.CategorySample.ReadCategory()
à UsageMonitor.Categories.Counters.UpdateCategory(String category)
ERRO (02:03:53.877) : UsageMonitor crashed trying to update the counters
DBUG (02:03:53.883) : L'élément a déjà été ajouté. Clé du dictionnaire : 'taille virtuelle (octets)' Clé ajoutée : 'taille virtuelle (octets)'
DBUG (02:03:53.887) : à System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
à System.Collections.DictionaryBase.System.Collections.IDictionary.Add(Object key, Object value)
à System.Diagnostics.CategorySample.ReadCategory()
à UsageMonitor.Categories.Counters.UpdateCategory(String category)
ERRO (02:03:54.878) : UsageMonitor crashed trying to update the counters
DBUG (02:03:54.884) : L'élément a déjà été ajouté. Clé du dictionnaire : 'taille virtuelle (octets)' Clé ajoutée : 'taille virtuelle (octets)'
DBUG (02:03:54.889) : à System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
à System.Collections.DictionaryBase.System.Collections.IDictionary.Add(Object key, Object value)
à System.Diagnostics.CategorySample.ReadCategory()
à UsageMonitor.Categories.Counters.UpdateCategory(String category)
ERRO (02:03:55.878) : UsageMonitor crashed trying to update the counters
DBUG (02:03:55.884) : L'élément a déjà été ajouté. Clé du dictionnaire : 'taille virtuelle (octets)' Clé ajoutée : 'taille virtuelle (octets)'
DBUG (02:03:55.889) : à System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
à System.Collections.DictionaryBase.System.Collections.IDictionary.Add(Object key, Object value)
à System.Diagnostics.CategorySample.ReadCategory()
à UsageMonitor.Categories.Counters.UpdateCategory(String category)
ERRO (02:03:56.879) : UsageMonitor crashed trying to update the counters
DBUG (02:03:56.885) : L'élément a déjà été ajouté. Clé du dictionnaire : 'taille virtuelle (octets)' Clé ajoutée : 'taille virtuelle (octets)'
DBUG (02:03:56.890) : à System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
à System.Collections.DictionaryBase.System.Collections.IDictionary.Add(Object key, Object value)
à System.Diagnostics.CategorySample.ReadCategory()
à UsageMonitor.Categories.Counters.UpdateCategory(String category)
ERRO (02:03:57.880) : UsageMonitor crashed trying to update the counters
DBUG (02:03:57.886) : L'élément a déjà été ajouté. Clé du dictionnaire : 'taille virtuelle (octets)' Clé ajoutée : 'taille virtuelle (octets)'
DBUG (02:03:57.891) : à System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
à System.Collections.DictionaryBase.System.Collections.IDictionary.Add(Object key, Object value)
à System.Diagnostics.CategorySample.ReadCategory()
à UsageMonitor.Categories.Counters.UpdateCategory(String category)
I rebuilt the performance counter on my OS before testing.
Re: Need some language testing for UsageMontitor
Posted: May 26th, 2018, 4:33 pm
by kounger
No errors with my German version of Windows.
usagemonitor.png
4.2.0 beta r3064 64-bit (May 13 2018) - English (1033)
Windows 10 Education 1803 64-bit (build 17134) - German (1031)
Path: C:\Program Files\Rainmeter\
SkinPath: D:\...\Documents\Rainmeter\Skins\
SettingsPath: C:\Users\...\AppData\Roaming\Rainmeter\
IniFile: C:\Users\...\AppData\Roaming\Rainmeter\Rainmeter.ini
Re: Need some language testing for UsageMontitor
Posted: June 23rd, 2018, 3:20 pm
by tjhrulz
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
Re: Need some language testing for UsageMontitor
Posted: June 24th, 2018, 6:49 pm
by Stone
OK the plugin works now - even in danish.
4.2.0 beta r3104 64-bit (Jun 23 2018) - Danish (1030)
Windows 10 Home 1803 64-bit (build 17134) - Danish (1030)
Re: Need some language testing for UsageMontitor
Posted: June 26th, 2018, 8:34 am
by fred_gaou
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)