Issues with version 0.23.13

[jtokach]

Hi all,

I know that sub is on vacation, but this will need to be addressed upon his return.  Yesterday morning my box shut itself down due to excessive temp; this was a first.  Upon reboot and later in the day, I recieved a file corruption message from windows (a little balloon in the system tray) stating that C:\Windows\Temp\JETE1.tmp was corrupt and unreadable.  It so happens that GBPVR was not functioning at all either after this message appeared.  

I rebooted, ran chkdsk and upon restart I noticed that my McAfee virusscan was 50% processor usage (on a hyperthreaded box, so really 100%).  When I stopped GBPVR, this ceased.  The McAfee On-Access scanner displayed that it was constantly scanning the Access lock file C:\Program Files\devnz\gbpvr\gbpvr.ldb.  I added an exclusion in McAfee to not scan this file and all is now good.  

So, what happened between versions to cause this?  I suppose only sub knows.  But I'm pretty sure this is what caused the corruption in the .tmp file and I'm certain I'll monitor processor usage after each install from now on.

Can someone confirm/deny this?

Windows XP SP2
2.8G PIV HT
McAfee Virusscan Enterprise Ed. v7.1.0
Engine 4.3.20
Dats 4415

[mikey]

Quote[/b] ]I rebooted, ran chkdsk and upon restart I noticed that my McAfee virusscan was 50% processor usage (on a hyperthreaded box, so really 100%). When I stopped GBPVR, this ceased. The McAfee On-Access scanner displayed that it was constantly scanning the Access lock file C:\Program Files\devnz\gbpvr\gbpvr.ldb.

This was probably the root cause of the problem. This file is created and deleted every time GB-PVR accesses it's database. I'm guessing it's just a brain dead feature of McAfee, which is causing it to virus scan this file a potential huge number of times. I use Norton AntiVirus and dont have this problem.

Now you've added it to the exclusion list the problem is probably gone.

[jtokach]

The lock file is created by access.

This behaviour didn't exist prior to the most recent release. Yes, the exclusion works, but this is not a fix for potential bug. If GBPVR has faulty code which is accessing the DB an extra 100 times per second we have a problem. The bug should be traced.