I'm afraid there is no magic bullet here. Then start adding back in extra things until you hopefully find out what your system doesn't like. You want to run your skins in as "vanilla" a way as possible, so we can ensure that Rainmeter itself, and skins just written using the built-in Rainmeter functionality, work ok. I'd start by eliminating HWiNFO, that nVidiaInspector software, and that 3rd-party font as well from the mix. Some conflict with hardware of some software you are running. Rainmeter in and of itself just doesn't have a problem with "leaks" of any kind, so it just has to be either something about the skins you are running, or perhaps, although less likely in my view, something particular about your setup. The point is to see if you can find out which skin or skins is causing the problem for you. If it starts to creep up after loading a particular skin or skins, then remove those and see if the problem goes away. Assuming it doesn't, then add another of the skins and repeat. By that I man load just one of your skins, restart Rainmeter, watch the CPU / Memory usage over time, and see if it "creeps" on you. The best advice I can give is to spend some time trying to isolate the issue. I'm not getting the problem you have, but then I can't really run that skin in a way that is an accurate test, as I don't have nVidia hardware or the same sensor setup you have. Somebody could install the skin and test if the same effect is happening on other PCs too? Hope somebody could have a look at the widgets in case the coding is causing this. !MYkC0SID!e7kutviTWfV-R0rU6Zrh3JB4GbaEGFHhpNNhNKnGvXY The plugin is updated to the latest version. It's a total of 9 widgets, where 5 of them are accessing HWiNFO plugin. I hope somebody with enough technological knowledge about Rainmeter could have a look at the widgets. Memory leak is not really the problem here, the CPU rising is the great problem here, as I'm using it on a notebook, where the high CPU usage makes the CPU stay at high clocks, killing the battery. When I start Rainmater it takes about 0.2-0.4% of CPU, after like 15 minutes it's already about 9% of CPU usage and still growing. and worst of all the every 2 to 5 minutes, it requires about 0.1% of more CPU. Hi, I rechecked and cleaned the whole skin again, but it still keeps happening. Hope this will be useful for somebody having the same issue. Disabling any compatibility mode fixed the issue instantly. I don't know what else to do.Īt the end it turned out I had Windows 7 compatibility mode enabled. Trying out Rainmeter 3.1,3.2 and 3.3, but it kept happening. I removed them inmediately from "My Documents" folder and removed all it's plugins from "%appdata%/Rainmeter/plugins" directory leaving only "HWiNFO.dll" there. I first noticed it happening when I was trying out some other 3rd party skins for rainmeter. What is going on there? Why is it doing this now? And why before not? Is there any way to know what is causing that? In the debug console it's not saying anything useful (No errors, no warnings, nothing, seems all OK). The same happens to the RAM usage, after some hours it raises till 300MB and even +500MB!! For a time it was working perfectly (0.1% of CPU usage and below 50MB RAM) no matter how much time it was running.īut now, after 30 minutes the CPU usage is between a constant 9 to 15%.Īfter one hour or two it gets up to 25% to 30% and raising!!!! (I'm on a i7 PC!!) There isn't any particular value in leaving open the "sensors" window for HWiNFO while you are setting up the skin, or ever really.Hello, I've made a simple skin to display some info from HwInfo. It is however, the best tool I have found for creating really robust Rainmeter skins that monitor sensor-based resources. It's not something that is particularly "plug and play" for the end-user. I'd be hesitant to widely distribute a skin that used it. I confess that configuring a skin to use HWiNFO is not entirely trivial. Use the skin - what it displays (er, in one of its windows) together with its code - to work out what code to put in one's own skin. (This yield two running programs with almost identical taskbar icons.) Obtain the skin from the page you linked and run the skin. Obtain and install the HwInfo application and configure it to run on startup and find its setting for the GPU sensor and enable that sensor. It seems one has to do all of the following.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |