2016-03-17, 21:00
I have set kodi in windowed mode. We'll see tomorrow.
2016-03-19, 19:47
Stil no change. Logs:
Debug kodi.log: http://xbmclogs.com/pbz4jya2l
Debug kodi.old.log: http://xbmclogs.com/pxuejwlxe
Debug kodi.log: http://xbmclogs.com/pbz4jya2l
Debug kodi.old.log: http://xbmclogs.com/pxuejwlxe
2016-03-20, 00:10
Kodi windowed mode on the desktop, largely uses windows routines for the display.
Looking over the debug logs doesn't bring up anything out of the ordinary, the second old.log is 504 Gateway Time-out and of course that would be the one with the issue at the end. At this point it looks like you have the issue regardless of iteration of Kodi. With that in mind, one last test will put a bit more certainty to the issue (suspect is handshaking), if it's possible to retain your set-up, but only using desktop of the monitor (taking the TV out of the equation) Kodi in windowed mode, do we get a crash eventually or NO. If it does crash we have some sort of germilin or memory leak.,
@scott967
I'm a little unsure if you are using extended, dual display or swapping, wondering if this issue might be related, can we go with only ONE display. let's try and keep handshaking out of this for the moment.
Looking over the debug logs doesn't bring up anything out of the ordinary, the second old.log is 504 Gateway Time-out and of course that would be the one with the issue at the end. At this point it looks like you have the issue regardless of iteration of Kodi. With that in mind, one last test will put a bit more certainty to the issue (suspect is handshaking), if it's possible to retain your set-up, but only using desktop of the monitor (taking the TV out of the equation) Kodi in windowed mode, do we get a crash eventually or NO. If it does crash we have some sort of germilin or memory leak.,
@scott967
I'm a little unsure if you are using extended, dual display or swapping, wondering if this issue might be related, can we go with only ONE display. let's try and keep handshaking out of this for the moment.
2016-03-20, 13:28
Thanks PatK for your thought over this. Last night it stopped again (which is expected, because I didn't change anything). But for the certainty of it, the logs:
Debug kodi.log: http://xbmclogs.com/pvoaekvi4
Debug kodi.old.log: http://xbmclogs.com/p5pezude4
Your suggestion is not completely clear for me. You want me to disconnect the computer from my AVR-receiver and tv, but keep the computer running as usual with Kodi in windowed-mode? I can do that. I will setup it like that tonight. I can connect tomorrow morning with remote desktop to see if kodi has crashed.
Please react if this is what you mean.
Debug kodi.log: http://xbmclogs.com/pvoaekvi4
Debug kodi.old.log: http://xbmclogs.com/p5pezude4
Your suggestion is not completely clear for me. You want me to disconnect the computer from my AVR-receiver and tv, but keep the computer running as usual with Kodi in windowed-mode? I can do that. I will setup it like that tonight. I can connect tomorrow morning with remote desktop to see if kodi has crashed.
Please react if this is what you mean.
2016-03-20, 17:07
Quote:You want me to disconnect the computer from my AVR-receiver and tv, but keep the computer running as usual with Kodi in windowed-mode?Yes, I'm trying to determine if the handshaking between the TV and PC is the villain, by doing this, you eliminate handshaking of the display, it's a native display to your system and there's no reason to have issues at all, next step would be a direct connect to the TV (to see if eliminating the AVR could be the root cause). At this point handshaking with the hardware is suspect. http://kodi.wiki/view/Displays (wiki) and this might be helpful http://forum.kodi.tv/showthread.php?tid=158432
additional check. http://forum.kodi.tv/showthread.php?tid=...pid2287586
2016-03-21, 20:53
Unfortunately no results. Still a crash. Last night I had de HDMI cable disconnected from the windows/kodi machine. After disconnecting I checked the status of kodi through Chrome remote desktop. It worked at that moment as expected. Just now I checked it again with Chrome remote desktop (without the HDMI cable plugged in). Kodi had crashed.
Somehow my Kodi Log Uploader refuses service as well. "Kodi Log Uploader error".... After I reinstalled the plugin I got these logs:
debug kodi.log: http://xbmclogs.com/p4bwauqpn
debug kodi.old.log: http://xbmclogs.com/poxphxfyl
Somehow my Kodi Log Uploader refuses service as well. "Kodi Log Uploader error".... After I reinstalled the plugin I got these logs:
debug kodi.log: http://xbmclogs.com/p4bwauqpn
debug kodi.old.log: http://xbmclogs.com/poxphxfyl
2016-03-21, 22:11
Still struggling with this issue on this side.
To eliminate a hdmi handshake issue, i plan on replacing the monitor.inf to fake a permanent 'monitor on' condition. Has anyone tried this yet?251833 (thread)
To eliminate a hdmi handshake issue, i plan on replacing the monitor.inf to fake a permanent 'monitor on' condition. Has anyone tried this yet?251833 (thread)
2016-03-23, 03:51
I have the same issue,
I went back to 15.2 and no longer have any problems.
But every time i try 16.0 or the 16.1 rc1 the freezing after idle returns
I went back to 15.2 and no longer have any problems.
But every time i try 16.0 or the 16.1 rc1 the freezing after idle returns
2016-03-23, 20:14
(2016-03-23, 03:51)bobtelco Wrote: I have the same issue,
I went back to 15.2 and no longer have any problems.
But every time i try 16.0 or the 16.1 rc1 the freezing after idle returns
I said I had the issue with 15.2 as well, but the other reactions make me doubt. I could be mistaken there. Could very well be the same issue.
2016-03-23, 21:32
If you think it may be a HDMI handshaking issue, try the "Pin 19 Trick". Just needs a bit of tape
http://forum.kodi.tv/showthread.php?tid=...pid1357945
http://forum.kodi.tv/showthread.php?tid=...pid1357945
2016-03-24, 06:51
(2016-03-16, 12:39)ZatarraNL Wrote: - TV never switches HDMI input.Related to http://trac.kodi.tv/ticket/16638
- PC always stays on.
- Denon receiver and TV are both switched off when activity is stopt.
- Denon receiver is switching input when switching activity.
When the AVR is turned off HDMI hotplugging takes place from your GPU driver's point of view in full compliance with specs.
With 16.0 Kodi upgraded to the more modern D3D11 framework and now some loose ends from the past show that need to be dealt with, whereas on D3D9 with 15.2 the issue MIGHT have been masked by a lost device now and then, though some users could always see it.
See referenced thread in the ticket for a test build soon that should fix this problem for most users seeing it. And where it does not it will log the necessary information that is needed to see what is happening here until we got a complete solution that deal with all similar issues users are reporting and a Pull Request can be made, so the devs can include the fix in an upcoming version whenever they decide to do so.
I have finished my first version of the patch but need to do my own testing first and add some additional logging before public testing.
2016-03-25, 11:34
I will try to disable the 19th pin from the HDMI cable. Allthough I doubt it is the solution because the crash happened just as well without any HDMI cables attached.
2016-03-27, 00:49
I'll echo scott967's experience... I am seeing similar behavior on Windows 8.1 x64 with Kodi 16.0, with just a single display (TV). When the TV is turned off and then turned back on hours later, Kodi is in screensaving mode (as expected). When I wake it up via keyboard, the UI renders but looks incomplete - and the UI is very slow to respond, every command takes 30-40 seconds to process. The solution seems to be to exit the app and then restart it. I only started experiencing this after I upgraded from 15.2 to 16.0.
2016-03-27, 10:11
I"ve the same problems here as well. (since kodi 16+)
My setup is plainsimple, a asus miniboard filled with an i5-3570k, 8 gig of mem and some hd space and using the i5's gpu abilities.
I connect through HDMI directly to my TV.
When i start kodi all goes fine, when i come back the next morning, it does react but as described my visual movement comes must later then my sound.
And it can take long to get a first responds, sometimes even 30 secs or more.
Last week i had another problem in my system which actually might help in seeking the villain. My cpu-fan wore down at night, i came back in the morning and found a hot cpu with kodi open. After trying to fix my fan and trying more test i finally replaced my fan, but stayed monitoring my system for several days to get a safe feeling about my system again. Now the thing ....
Kodi idle directly after start for an hour or more, cpu temperature 34 celcius. When i come back next day, same kodi not have done anything user controlled. temperature 60 celcius. BUT if i look to the cpu usage it's minimum like say nothing at all. Though my cpu (as all in the intel iX series) has a gpu. As i can check what my cpu is doing but not my gpu. I Expect overtime on the gpu side.
[edit]The problem also occurs when kodi has been idle on the background for a couple of hours when i've playing some browsergames.
Ergo pc never lost contact with the tv, nor did the tv ever went into blackscreen/hibernate.
My setup is plainsimple, a asus miniboard filled with an i5-3570k, 8 gig of mem and some hd space and using the i5's gpu abilities.
I connect through HDMI directly to my TV.
When i start kodi all goes fine, when i come back the next morning, it does react but as described my visual movement comes must later then my sound.
And it can take long to get a first responds, sometimes even 30 secs or more.
Last week i had another problem in my system which actually might help in seeking the villain. My cpu-fan wore down at night, i came back in the morning and found a hot cpu with kodi open. After trying to fix my fan and trying more test i finally replaced my fan, but stayed monitoring my system for several days to get a safe feeling about my system again. Now the thing ....
Kodi idle directly after start for an hour or more, cpu temperature 34 celcius. When i come back next day, same kodi not have done anything user controlled. temperature 60 celcius. BUT if i look to the cpu usage it's minimum like say nothing at all. Though my cpu (as all in the intel iX series) has a gpu. As i can check what my cpu is doing but not my gpu. I Expect overtime on the gpu side.
[edit]The problem also occurs when kodi has been idle on the background for a couple of hours when i've playing some browsergames.
Ergo pc never lost contact with the tv, nor did the tv ever went into blackscreen/hibernate.
2016-03-28, 23:26
I will also jump onto this discussion having the same issues. The problem only arose after moving from 15.2 to 16.0/16.1-RC1. The minor difference I have is that when Kodi is frozen, rss has stopped and that no keyboard or mouse activity will wake it up. Not related to any overnight event as it only takes an hour or two of the HTPC being idle for the freeze-up to occur when Kodi is active on the HTPC but the TV is active on another Input source as well (Satellite for example). I have disabled all screen saving events in order to rule out as a cause and do not allow my HTPC to Sleep or Hibernate (ever).
HTPC is Windows 10 Pro 64 bit with Up-to-date patches running in Dual Monitor Mode with identical 1080p X 1920 resolutions on NVIDIA GeForce GT630 DirectX v12. Setup is similar to most reporting here with 1 caveat: DVI to HDMI connection to desktop monitor; HDMI connection to Yamaha Network Receiver - switched over single HDMI connection to Samsung UHD 3D TV (all current year hardware).
HTPC is Windows 10 Pro 64 bit with Up-to-date patches running in Dual Monitor Mode with identical 1080p X 1920 resolutions on NVIDIA GeForce GT630 DirectX v12. Setup is similar to most reporting here with 1 caveat: DVI to HDMI connection to desktop monitor; HDMI connection to Yamaha Network Receiver - switched over single HDMI connection to Samsung UHD 3D TV (all current year hardware).
