[Milhouse]

It started happening after approximately 10 minutes. I'm not sure where that corresponds to in the debug log, but I'm guessing it has something to do with the flood of...

"16:00:22 1597.086060 T:2760893520 DEBUG: JSONRPC: Incoming request: [{"id":0,"jsonrpc":"2.0","method":"Player.GetActivePlayers"},{"id":1,"jsonrpc":"2.0","method":"Application.GetProperties","params":{"properties":["volume","muted"]}}]"

Are you by any chance using Yatse on an Android phone or tablet? Yatse floods the device with JSON queries rather than use JSON notifications to monitor client changes. It shouldn't cause the problems you mention, but it's a non-scalable solution so who knows what happens if you have multiple Android devices running Yatse and flooding a single XBMC client (poor Pi).

Anyway, it's a very long log - unless you can pin down an approximate time it's difficult to know what is going on or what is causing it. I normally tail the log over ssh, allowing you to spot when abnormal behaviour starts.