Poor performance: log full of Mpeg2Reader seeking to pos=0 messages

[lotus]

I have a fault, which has occurred several times but I am unable to see why as the log files very rapidly become full of one message. A sample of the messages is:

Mon 2/5 19:42:01.935 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.935 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.935 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.936 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.937 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.937 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.937 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.937 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.937 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.937 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.937 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.938 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.939 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.940 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.941 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.941 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.941 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.941 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.941 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.941 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.941 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.941 Mpeg2Reader seeking to pos=0
Mon 2/5 19:42:01.942 Mpeg2Reader seeking to pos=0

Sage service is using around 80% of the CPU and 250MB of memory but still working. Menus are very slow (10+ seconds per action) but if you are patient they can be used. I am using version 6.0.19 with two PC clients and two MVPs.

I have seen other posts with this message but no solution and I don't know what area to investigate.