this is part of the real-time inventory. It shouldn't consume this amount of CPU. Seems like it's hung up. If you kill it, does it reoccur? Here is a good link to do some debug logging if needed:
Did this issue ever return? I'm just now starting to dig on a report of a similar issue.