Seeker waiting for 292 million years??

[Enormous]

I'm consistently getting this line output to my logs, and whenever it does this (on startup), the server uses insane amounts of CPU. It also does not run the recordings scheduler, so SageTV just sits there, churning away, doing nothing. Sometimes it'll settle down and actually start to work, other times it won't.

-snip-
Mon 12/11 18:36:53.565 Seeker waiting for 153722847849456 mins.
-snip-
Mon 12/11 18:39:17.374 Seeker waiting for -19431459 mins.

So it seems like sometimes Seeker wants to wait for millions of years, or it wants to travel back in time.

I've filed a bug concerning this, but am wondering if anyone else has seen this sort of thing.

[Motofreak75]

I don't about you, but I rather find another hobby, if my seeker told me to wait that long

[Enormous]

Originally Posted by Motofreak75

but I rather find another hobby, if my seeker told me to wait that long

While that is tempting, I would really like to know if anyone has seen something like this before. I'm still trying to figure out why Sage will start consuming all of the CPU resources that it can, and not let them go. All the while, seemingly doing nothing (no log calls, etc.). I even just got done upgrading my mobo/ram/CPU in order to fix this. Anyone?