The bug appears to affect every meter and every plugin measure. It occurs for every possible Update rate, however for slower Update rates it is not that noticeable in immediate CPU usage, but it is still visible in CPU time used by Rainmeter process after some time.
For testing purposes I have run 10 same skins (see examples below) and measured CPU usage in Windows Task Manager, as it was enough to see the difference in immediate CPU usage.
Example 1 (CPU usage 00 % -> 05 %):
Code: Select all
[Rainmeter]
Update=50
[Background]
Meter=Image
X=0
Y=0
W=60
H=60
UpdateDivider=-1
SolidColor=021920cc
[MeasureAudio]
Measure=Plugin
Plugin=Win7AudioPlugin
[MeasureAudio2]
Measure=Plugin
Plugin=Win7AudioPlugin
[MeasureAudio3]
Measure=Plugin
Plugin=Win7AudioPlugin
Code: Select all
[Rainmeter]
Update=50
[Background]
Meter=Image
X=0
Y=0
W=60
H=60
UpdateDivider=-1
SolidColor=021920cc
[MeasureUsage1]
Measure=CPU
[MeterStr1]
Meter=String
Y=5
MeterStyle=StringStyle
[MeterStr2]
Meter=String
Y=19
MeterStyle=StringStyle
[MeterStr3]
Meter=String
Y=33
MeterStyle=StringStyle
[StringStyle]
StringAlign=Right
X=39
FontColor=6dd6f4
FontFace=Myrian Pro
FontSize=8
AntiAlias=1
MeasureName=MeasureUsage1
Laptop - HP Probook 6570b
Windows 10 64-bit
Intel Core i5-3210M @ 2.50 Ghz
Rainmeter 4.0 (3.3 same problem)