<solved> [NPVR 2.3.6] resource-exhaustion / memory leak

[ShiningDragon]

Yes, of course. You can access to my MediaCenter via UltraVNC. I'll send you the login data via pn.

[sub]

lol - that didnt work out. Me and German descriptions for everything dont seem to work well together. I'll have to think of something else.

Can you see if this patch makes any difference?

Keep your original file though - this one is only temporary and disables stuff, so you'll need to restore the original file afterwards.

[ShiningDragon]

lol - that didnt work out. Me and German descriptions for everything dont seem to work well together.

Nobody is perfect. XD

Ah, nevermind. I know this situation if my polish neighbour comes over with her polish windows ... it's every time fun trying fixing something.

Can you see if this patch makes any difference?

I'll try it out immediately. Thank you. =)

Since enabling the swapfile, the usage of "Private Bytes" stay at the same level, but the other bars raise exactly like before.
So no real change on this front.

[sub]

What is the translation of that green line?

Did you install that patch? That basically disables all extra processing NextPVR does during playback, so you removes logic that does OSD graphics, watches for subtitles etc.

[ShiningDragon]

The translation of the green line, called "Auslagerungsseiten (Bytes)" SHOULD be, i am not 100% sure, "swap pages (bytes)", while the red one "Auslagerungsdatei (Bytes)" is the "swapfile (Bytes)".

Yep i had installed the patch. It didn't made any difference.

I had meanwhile the thought if it would be a problem that the files were served via lan, so i copied a few episodes to the mediacenter and played them locally. But even here: no difference.

No background processing too. Mhm, i have atm no idea for what i should look. You saw the mediacenter: slimline, not much software installed.

[sub]

The translation of the green line, called "Auslagerungsseiten (Bytes)" SHOULD be, i am not 100% sure, "swap pages (bytes)", while the red one "Auslagerungsdatei (Bytes)" is the "swapfile (Bytes)".

Ah right... I'm wasnt really interested in that line. I'm interested in Private Bytes, Virtual Bytes and Working Set - which are what give us a real indication of the amount of memory being used. Do any of those show it increasing?

[ShiningDragon]

Private Bytes is holding it's level with patch and swapfile enabled. No raising.
Virtual Bytes are growing steady.
Working set i have to test again ( hopefully i'll find the right translation for this, the microsoft translator doesn't do it ;D )
But for now i have to go to bed. I'll post tomorrow more data and let the mediacenter running the whole night WITH swapfile, to see if it's freezing again.

[Britney Spears]
"Oooops, it happened again ..."
[/Britney Spears]

Just woke up and saw the (usual) standing picture of the show. NPVR died again, this time even WITH swapfile (did i mentioned before already, that i never needed one before on this machine?).

The windows eventviewer doesn't tell anything. It's clean, until the point where npvr just stopped working. No reason why. The performance counter didn't saved anything. -.-

I'll make now a last run with your patch and see what happens.

I have attached the logs of the last run, perhaps you can see something "special".


EDIT:
sub, what's going on with nrecord?

Code:

2012-01-21 07:16:46.597    [ERROR][7]    Unexpected error in PurgeOldDeletes(): System.Data.SQLite.SQLiteException: Insertion failed because the database is full
database or disk is full
   bei System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
   bei System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
   bei System.Data.SQLite.SQLiteDataReader.NextResult()
   bei System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
   bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
   bei System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
   bei NUtility.RecentlyDeleted.PurgeOldDeletes()
(...)
2012-01-21 08:20:28.060    [ERROR][7]    Unexpected error in PurgeOldDeletes(): System.Data.SQLite.SQLiteException: Insertion failed because the database is full
database or disk is full
   bei System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
   bei System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
   bei System.Data.SQLite.SQLiteDataReader.NextResult()
   bei System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
   bei System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
   bei System.Data.SQLite.SQLiteCommand.ExecuteNonQuery()
   bei NUtility.RecentlyDeleted.PurgeOldDeletes()

The display of the iMON VFD (no, not the npvr plugin; just the normal clock) stopped already at 07:29 in the morning. The logfile is full of this errormessages related to the database.

Idea:
If the freeze repeats, then i'll stop nrecord.exe service and shutdown ntray.exe . I can't understand why nrecord starts producing such errormessages related to the database. The mediacenter is just a client; the npvr 2.3.6 based server doesn't have those errormessages.

[whurlston]

How big is your database? You might try running VACUUM on it using a sqllite database manager like sqliteadmin

[ShiningDragon]

The database on the server is just around 25 MiB in it's size. The nrecord.log on the server is absolutely clean, no errormessage from the mediacenter client or something similar.

On the mediacenter itself it's just 28 KiB in size, i've just ran the nextpvr.exe -updatedb hoping fixing any possible error (yeah, i know it should using the server db ... but i don't have many options left atm). ^^

One interesting thing is, that npvr itself is running fine after start. If you're start watching media, all is fine too. And then after hours it's producing db related errors on the client.

[whurlston]

25MB is not a problem so I'm not sure what the issue is. Sorry