2006-01-02, 06:08 AM
I've been working through my GB-PVR skin, but I'm finding that I run out of memory after 2-3 days. I don't have any errors listed in the logfile until the PendingRecording panel tries to refresh, then it throws an "Out of Memory" error. The recording service is still running, but the GUI freezes and GB-PVR memory usage is around 149,000k.
The reason I suspect that the skin is causing this issue is (1) no one else has reported this issue with the latest release and (2) it's only been in the last two weeks since I'd tweaked the skin a bit more.
So, after the long preamble, the question I have is: Is it more memory-efficient to use button graphics and the DrawImage method (the skin refers to six different button.png files), or is it better to use the DrawRoundedRect method for button graphics?
The reason I suspect that the skin is causing this issue is (1) no one else has reported this issue with the latest release and (2) it's only been in the last two weeks since I'd tweaked the skin a bit more.
So, after the long preamble, the question I have is: Is it more memory-efficient to use button graphics and the DrawImage method (the skin refers to six different button.png files), or is it better to use the DrawRoundedRect method for button graphics?
[SIZE=1]
HD PVR: nPVR 4.2.2 with VLC 3.0.3 Std Skin
ASRock H170M Pro4 LGA 1151 Intel H170 HDMI-out, Intel Core i3-6100 3.7GHz, 16GB DDR4 2400, Win7 Ultimate x64, Hauppauge Colossus, 1x250GB SSD (System), 1x1TB SATA (Recordings), DirecTV HD22 STB, dtvTune.exe Ethernet channel changer
Running Samsung Smart TV plugin from Fred250
HD PVR: nPVR 4.2.2 with VLC 3.0.3 Std Skin
ASRock H170M Pro4 LGA 1151 Intel H170 HDMI-out, Intel Core i3-6100 3.7GHz, 16GB DDR4 2400, Win7 Ultimate x64, Hauppauge Colossus, 1x250GB SSD (System), 1x1TB SATA (Recordings), DirecTV HD22 STB, dtvTune.exe Ethernet channel changer
Running Samsung Smart TV plugin from Fred250