I have discovered that an issue I was struggling with has (re?)occured and seems to be present in current patch. I already made a construct to avoid the problem, but it is not rock-solid it would seem, so I would appreciate some advice from you or anybody else with more overview of the inner workings of Xbmc than myself.

Problem;
-when Gui-thread drives the wakeup we display the progress-dialogue while periodically pinging to see if server gets online.
-to maintain the dialog there is the dialog::Progress() function which does various stuff and also ends up in Application::Process() and Application::ProcessSlow()
-ProcessSlow in turn can also do stuff that does remote MySQL or FileAccess and so there is a recursive situation that breaks the whole thing
-To avoid the situation, I put in a function to disallow execution of ProcessSlow() while waiting for server but apparently there are still cases where this recursive loop happens (I suspect it is in distribution of suspend/wakeup events)

Any advice howto handle this would be appreciated