2013-10-01, 02:47
With g_TextureManager.FreeUnusedTextures(0) I don't really see an obvious performance difference when browsing rapidly through Movies and displaying different 1080p fanart.
There were a few OMX errors however, that are not timeout related:
It seems that a 512MB Pi with 256/256 split is capable of handling 1080p artwork and a 1080p/32bpp GUI with the default 5 seconds texture deletion interval, so reducing this deletion interval doesn't seem necessary unless there's a better way to test.
There were a few OMX errors however, that are not timeout related:
Code:
01:36:59 T:2902631504 ERROR: COMXCoreComponent::SetStateForComponent - OMX.broadcom.image_decode failed with omx_err(0x80001000)
01:36:59 T:2902631504 ERROR: COMXCoreComponent::SetStateForComponent - OMX.broadcom.image_decode failed with omx_err(0x80001000)
...
01:37:53 T:2902631504 ERROR: COMXCoreComponent::WaitForCommand OMX.broadcom.image_decode wait timeout event.eEvent 0x00000000 event.command 0x00000002 event.nData2 320
01:37:53 T:2902631504 ERROR: COMXCoreComponent::DisableAllPorts WaitForCommand error on component OMX.broadcom.image_decode port 320 omx_err(0x7fffffff)
01:37:53 T:2902631504 ERROR: COMXCoreComponent::Initialize - error disable ports on component OMX.broadcom.image_decode omx_err(0x7fffffff)
...
01:37:55 T:2902631504 ERROR: COMXCoreComponent::WaitForCommand OMX.broadcom.image_decode wait timeout event.eEvent 0x00000000 event.command 0x00000000 event.nData2 2
01:37:55 T:2902631504 ERROR: COMXCoreComponent::WaitForCommand - OMX.broadcom.image_decode failed with omx_err(0x7fffffff)
01:37:55 T:2902631504 ERROR: COMXTexture::Decode - Error alloc buffers (80001012)It seems that a 512MB Pi with 256/256 split is capable of handling 1080p artwork and a 1080p/32bpp GUI with the default 5 seconds texture deletion interval, so reducing this deletion interval doesn't seem necessary unless there's a better way to test.
