[marhutchy]

Before you mention it - I know it's beta.

However, this might be important.
Third time I'm getting a memory leak. I left Isengard idle for a while (paused a show once), and then bam!

LOG

[Ned Scott]

Can you post another log with debugging turned on?

[marhutchy]

Can you post another log with debugging turned on?

Sure, but would that log have info on the leak?

[Ned Scott]

It's very possible.

[Martijn]

Can you post another log with debugging turned on?

Sure, but would that log have info on the leak?

Leaks are usually not logged. Only errors but those could possibly indicate where it leaks

I would advise to at least install latest nightly
http://mirrors.xbmc.org/nightlies/win32/

[marhutchy]

Can you post another log with debugging turned on?

Sure, but would that log have info on the leak?

Leaks are usually not logged. Only errors but those could possibly indicate where it leaks

I would advise to at least install latest nightly
http://mirrors.xbmc.org/nightlies/win32/

Here's log nonetheless. LOG

I'm not familiar with nightlies.
I see where the last modified date is almost daily.
Would I have to install each new release?

EDIT: Turned on debug during memory leak. LINK

[marhutchy]

It's very possible.

Can you post another log with debugging turned on?

Sure, but would that log have info on the leak?

Leaks are usually not logged. Only errors but those could possibly indicate where it leaks

I would advise to at least install latest nightly
http://mirrors.xbmc.org/nightlies/win32/

I installed the nightly build KodiSetup-20150611-0e9bde4-master, but the memory leak still occurred.

[Ned Scott]

There is some warnings relating to an add-on that "may" cause memory leaks, but I'm not sure which add-on. I'm not sure if the log isn't saying which, or I've just forgotten how to figure out what add-on goes with what message.

[marhutchy]

I'm suspicious of Watchdog.
I'm going to find out by method of elimination.

[marhutchy]

Can you post another log with debugging turned on?

Sure, but would that log have info on the leak?

Leaks are usually not logged. Only errors but those could possibly indicate where it leaks

I would advise to at least install latest nightly
http://mirrors.xbmc.org/nightlies/win32/

There is some warnings relating to an add-on that "may" cause memory leaks, but I'm not sure which add-on. I'm not sure if the log isn't saying which, or I've just forgotten how to figure out what add-on goes with what message.

Here's another log with debugging turned on. Memory leak started about 12:40 when I started playing a mkv file and trakt add-on notification appeared.

LOG (before fresh install)

EDIT: I did a fresh install, after being idle for most of the day, nothing happened. I started playing a movie - memory leak.
Here's another log after fresh install

LOG (after fresh install)

[marhutchy]

...

...

Most recent log.
Debugging turned on.
Suspected add-ons (trakt and lazytv) disabled, but I still got the leak.

LOG

[k4sh1n]

You may have thrashing of vram to hdd page file when trying to render content.
Suggest change frame rate to 60Hz and make sure all H/W acceleration if off and render is software.
Run a hdd check with Crystal disk info and see how you go

[marhutchy]

You may have thrashing of vram to hdd page file when trying to render content.
Suggest change frame rate to 60Hz and make sure all H/W acceleration if off and render is software.
Run a hdd check with Crystal disk info and see how you go

Here's what Crystal showed me http://pastebin.com/bxGzKSKp

I'll do the other part and test it.
Where do i change the frame rate?

I'm trying to remember when it started.
I think it's about 2 days after upgrading to Isengard.

[k4sh1n]

Frame rate is via windows/GPU display settings

[marhutchy]

Frame rate is via windows/GPU display settings

Oh, I figure as much.
Intel GMA had it 60, but Windows 7 built-in monitor setting had it at 59. I changed it to 60.

Still testing...