05-13-2012, 02:13 AM
Based on legend80 and thewildpendulum's cases so far, my initial hypothesis is that the new ffmpeg embedded in the new Xuggle may be using the new Intel AVX instructions. Newer CPUs (Sandy Bridge and Ivy Bridge) have a new instruction set called AVX which extends SSE. When in 64-bit mode, the new ffmpeg may be using AVX and due to a bug in ffmpeg's AVX code or in the compiler, it becomes unstable. Older generation CPUs are not affected since ffmpeg falls back to SSE. Also 32-bit mode is not affected since AVX is only available in 64-bit mode.
This hypothesis still needs to be proven though. legend80 and thewildpendulum, try running r2552 in 64-bit mode after disabling AVX and see whether it's stable. If I'm not mistaken, I believe AVX can be disabled through the mainboard's BIOS settings. If it's possible to disable AVX, please perform the test to prove or disprove my hypothesis. Thanks!
This hypothesis still needs to be proven though. legend80 and thewildpendulum, try running r2552 in 64-bit mode after disabling AVX and see whether it's stable. If I'm not mistaken, I believe AVX can be disabled through the mainboard's BIOS settings. If it's possible to disable AVX, please perform the test to prove or disprove my hypothesis. Thanks!