[2013-04-10 11:57:37,054] [62850 ] [MPMain ] [ERROR] - D3D: InitializeDeviceObjects - Exception: System.ObjectDisposedException: Auf das verworfene Objekt kann nicht zugegriffen werden.
Objektname: "MediaPortalApp".
bei System.Windows.Forms.Control.CreateHandle()
bei System.Windows.Forms.Form.CreateHandle()
bei System.Windows.Forms.Control.get_Handle()
bei MediaPortalApp.InitializeDeviceObjects()
bei MediaPortal.D3D.InitializeDevice()
last one seems to be a fonengine system, you will replace it anyway so I don't care much about it[2013-04-10 11:57:29,352] [55147 ] [34 ] [ERROR] - Exception: System.AccessViolationException: Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist.
bei MediaPortal.GUI.Library.DXNative.FontEnginePresent3D(Int32 fontNumber)
bei MediaPortal.GUI.Library.GUIFontManager.Present()
bei MediaPortal.GUI.Library.GUILayerManager.Render(Single timePassed)
bei MediaPortalApp.RenderFrame(Single timePassed) Message: Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist. Site : Void FontEnginePresent3D(Int32) Source : Core Stack Trace: bei MediaPortal.GUI.Library.DXNative.FontEnginePresent3D(Int32 fontNumber)
bei MediaPortal.GUI.Library.GUIFontManager.Present()
bei MediaPortal.GUI.Library.GUILayerManager.Render(Single timePassed)
bei MediaPortalApp.RenderFrame(Single timePassed)
[2013-04-10 11:57:29,353] [55148 ] [34 ] [ERROR] - RenderFrame exception Es wurde versucht, im geschützten Speicher zu lesen oder zu schreiben. Dies ist häufig ein Hinweis darauf, dass anderer Speicher beschädigt ist. Core bei MediaPortal.GUI.Library.DXNative.FontEnginePresent3D(Int32 fontNumber)
bei MediaPortal.GUI.Library.GUIFontManager.Present()
bei MediaPortal.GUI.Library.GUILayerManager.Render(Single timePassed)
bei MediaPortalApp.RenderFrame(Single timePassed)
Saw this when changing themes a couple of time. I acutally had to use configuration.exe and reset stuff as MP didn't load anymore. I think I created a Mantis issue for it, but probably closed it as I could not reproduce on demand. Will not fix as I plan to replace the font engine anyway.naaah, just wanted to change teh skin again and got a exception and MP crashed hard.
You see that this messages comes all the time:What infinite loop???
But I hit only once F5, so I assumed it is a infinite loop[2013-04-10 11:46:14,212] [55914 ] [MPMain ] [ERROR] - ProcessWindows exceptionystem.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
Saw this when changing themes a couple of time. I acutally had to use configuration.exe and reset stuff as MP didn't load anymore. I think I created a Mantis issue for it, but probably closed it as I could not reproduce on demand. Will not fix as I plan to replace the font engine anyway.
Probably because it get called over and over again when stuff is rendered?You see that this messages comes all the time:What infinite loop???
But I hit only once F5, so I assumed it is a infinite loop[2013-04-10 11:46:14,212] [55914 ] [MPMain ] [ERROR] - ProcessWindows exceptionystem.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
Was not sure when I get a string and when not. Thanks for testing.only the logging in the error.log seems a bit wrong oO That's the last regression I see so far...
There are several issue in Skin changing. But that part was not touched at all in regards what is done. Has the same bugs as stock 1.3.0. What can be possible is that you now see bugs that were masked in 1.3.0 by constant D3D device reset and therefore went unnoticed.ahh one regression left! If you change the skin inside MP the font isn't changed.