I get strange, sporadic and unreplicable issues when running videos with a modified omxplayer on raspberry pi 2 models.
Practically the video gets stuck on a frame and audio stops, sometimes the time goes on (given by a OMX Scheduler component), sometimes also the time freezes.
The system is responsive: killing the omxplayer process and running it again restores the normal condition. Apparently there were no VRAM leaks, just the videocore got stuck for an unknown reason. I have also ~35 raspberry pi 1 model B that instead never show this problem.
vcdbg log msg doesn't anything valuable, nor dmesg says anything. Sometimes also rendered frames get corrupted (see the attached jpeg). One interesting thing is that starting the whole process with affinity set to a single core seems to mitigate the problem. Also, as long as the problem happens only on raspberry pi2, I think maybe there is something that doesn't work well with multicore systems.
kernel is 3.18.7 and firmware version is:
Feb 14 2015 22:23:03
Copyright (c) 2012 Broadcom
version 7789db485409720b0e523a3d6b86b12ed56fd152 (clean) (release)
I would ask if any bug of the kind I explained above has been corrected lately, so upgrading the firmware of these production machines would help solve this problem.