problems with v0.98.8

[gabeweisz]

I'm suddenly getting the "database is locked" error as well - for me it's sometimes happening as soon as my computer boots (GBPVR is in the startup group)

[gEd]

I just received database is locked error with recording service at 100% load. I had rebooted pc as it had hung (hardware problem) and there was a recording already scheduled to go. (F1)

01/10/2006 13:46:35.343 INFO [4] Starting remoting service
01/10/2006 13:46:35.843 INFO [4] Start GB-PVR web on: 7647
01/10/2006 13:46:37.968 INFO [5] Found new programme requiring recording: F1: Chinese Grand Prix Live
01/10/2006 13:46:38.375 INFO [11] LiveTV File Removal Thread Started
01/10/2006 13:52:22.578 ERROR [5] Unabled to save ScheduledRecording: The database file is locked
database is locked
01/10/2006 13:52:27.671 ERROR [5] at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
at System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
at GBPVR.Backend.Common.x396614b3dae3b1da.xc979432fcc5a510a(ScheduledRecording xe41d2b9d98dc1269)
01/10/2006 13:52:32.671 INFO [13] Parallel Processing thread starting...
01/10/2006 13:52:32.875 ERROR [5] Found expired lease. Stopping recording.
01/10/2006 13:52:32.875 INFO [5] Recording is unusually small. Giving second chance: R:\Recordings\F1 Chinese Grand Prix Live\F1 Chinese Grand Prix Live_20061001_13301600.mpg (0)

[sub]

Also, on the memory question, is it normal for the Recording Service to take up 115,000K of memory, even when nothing is being watched or recorded? This has coincided with the whole computer grinding to a halt, and between them I have seen the GBPVR.exe and the recording service use over 150,000k before. Is this unusually high, or do I just need more memory to cope with it?

This can be normal. GB-PVR uses quite a bit of memory during the EPG updates. The more channels and days of listings, the more memory it uses. When it is finished the EPG update it releases the memory back to .NET....but, the way .NET memory management works means that it will not free the memory back to the operating system until the operating system informs it that it is running critically low and really needs the memory. (.net holds on to the memory on the assumption that if you needed that much in the past, you'll probably need it again sometime in the future)

This is nothing new for v0.98.8. Its still using pretty much the same amount of memory as all previous versions.

[frazer]

OK, thanks for that; maybe the huge French xml file I have is causing the memory problems then- it has about 140 channels in it! I figured that was the cause during an epg update, but didn't realise it would persist.

Unfortunately, I can't seem to edit out just the channels I want from the file; I tried the xmltv_grep facility, but could only edit out one channel at a time, rather than the eight I want, even though the instructions suggest it should be possible. Anyone out there using this successfully?

Thanks again,

Frazer

[rastyk]

I had problems with v0.98.8, with the database. I was able to work around this by reverting to the .mdb database by changing the config.xml. GB-PVR is really cool, this is a good group and I've been reading through these boards although I haven't played with GBPVR in a long while. The fix I used here may not be the best, but I haven't found other things to try yet. I hope this info helps.

I have a sempron 2800, xp, PVR-350, plextor TV-402U (although was having the problem before). I'm using zap2it and getting 4 days worth on about 80 stations (trying to). xp is installed, with no other applications except for video capture bundles and itunes.

I have reinstalled gbpvr many (5?) times to try to get rid of this database issue. The problems are that the software hangs, and gets a "database is locked" message. reinstalls only help for awhile. Other functions were really, really slow. the EPG update didn't work. I got this error message once (not sure what I was doing at the time, as I found it later on):

EventType : clr20r3 P1 : gbpvrrecordingservice.exe P2 : 1.0.2445.14611
P3 : 38 P4 : system.data.sqlite P5 : 1.0.30.1 P6 : 44a7e70d
P7 : 11f P8 : 2e P9 : system.data.sqlite.sqlite

In any case, pointing to the .mdb brings this back to life. Menus are snappy and everything works well.