home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
MediaPortal Invisible on Resume from Hibernate
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Sebastiii" data-source="post: 1197364" data-attributes="member: 60104"><p>Maybe it's a side effect of GPU drivers crash :</p><p></p><p>"10/3/2016 8:47:05 AM";"Display";"(0)";"Warning";"Display driver <strong>igfx</strong> stopped responding and has successfully recovered.";"4101"</p><p></p><p>and from MP.log :</p><p>[2016-10-03 08:47:33,377] [Log ] [MPMain ] [DEBUG] - GUIFont:texture disposing:0 debug</p><p></p><p>So 30 secs in between (this delay comes from the 30 secs is the option delay).</p><p>So the drivers crash and recover but we know that when it happen MP can't work after that and this is surely why we get the dispose and after all kind of errors messages about GPU.</p><p></p><p>I think we can't do nothing right now about that because when testing/simulate the crash MP or i would say .NET didn't know/detect the new D3D GPU from the current Form Window instance lol.</p></blockquote><p></p>
[QUOTE="Sebastiii, post: 1197364, member: 60104"] Maybe it's a side effect of GPU drivers crash : "10/3/2016 8:47:05 AM";"Display";"(0)";"Warning";"Display driver [B]igfx[/B] stopped responding and has successfully recovered.";"4101" and from MP.log : [2016-10-03 08:47:33,377] [Log ] [MPMain ] [DEBUG] - GUIFont:texture disposing:0 debug So 30 secs in between (this delay comes from the 30 secs is the option delay). So the drivers crash and recover but we know that when it happen MP can't work after that and this is surely why we get the dispose and after all kind of errors messages about GPU. I think we can't do nothing right now about that because when testing/simulate the crash MP or i would say .NET didn't know/detect the new D3D GPU from the current Form Window instance lol. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Quality Assurance
Bugreports
Archive
MediaPortal Invisible on Resume from Hibernate
Contact us
RSS
Top
Bottom