Yeah, I do not expect an answer either, not only because my question is large (and vague) but because the few similar questions I bumped into when googling about the error didn't have any solutions. Debugging a general streaming error is not easy.
I even tried to get it to work by destroying the pipeline and clean up everything when I got the EOS message and rebuild it again afterwards, this resulted in very similar (if not exact) results as seeking to the beginning. It seems to be some kind of memory problem, e.g. that I do not free something and that gstreamer runs out of some kind of internal buffer, but that is just speculation and as the actual setup of the pipeline as well as the handling (and seeking) are all in the GStreamer SDK tutorials my code should be correct ...
About sfeMovie; I have built it on Windows with everything that ffmpeg gives us. I got it to loop (not perfect but good enough, by stopping and playing when the movie reaches its end) and run it for about 26 hours (before I turned it off), which is great.
I would love to help out with the project, I just need to find the time. Performance is probably the most important thing right now and after that looping, I am not that interested in seeking. When I did the texture upload code from GStreamer to OpenGL I got a pretty nice performance boost when I switched from using sfml textures, using the update function, to using PBO ping ponging which makes it possible to stream texture data asynchronously without blocking the CPU. Is that something that may help the sfeMovie project or do you want me to look into something else?
// Zap