Kodi Community Forum

Full Version: [MAC] MacMini3,1 taking a long time to exit XBMC
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I am using a MacMini3,1 with XBMC 10.1. When I go to exit XBMC sometimes is can take 40 seconds or longer to finally exit. I can't seem to figure out why. I have looked at the debug log but there is nothing in there that stands out. Is this happening to anyone else?

By the way, I have noticed that in the debug log that it reports "Platform: Mac OS X (10.7.0 i386)". Is there a reason why XBMC reports I am using OS X 10.7.0 when I am actually using OS X 10.6.7?

debug log
Quote:I am using a MacMini3,1 with XBMC 10.1. When I go to exit XBMC sometimes is can take 40 seconds or longer to finally exit. I can't seem to figure out why. I have looked at the debug log but there is nothing in there that stands out. Is this happening to anyone else?

Definitely looks like an issue with curl, which points to network issues. You can see a lot of errors below in-amongst the delays you're getting (20 seconds between 15:16:35 and 15:16:55 below)

Code:
15:16:07 T:2955628544 M:1905176576   DEBUG: FileCurl::Close(0xb02b4db4) http://www.google.com/
15:16:07 T:2955628544 M:1905176576    INFO: easy_aquire - Created session to http://74.125.19.103
...
...
15:16:35 T:2956161024 M:1897267200 WARNING: FillBuffer: curl failed with code 28
15:16:35 T:2956161024 M:1897267200   DEBUG: FillBuffer: Reconnect, (re)try 1
15:16:55 T:2956161024 M:1889890304 WARNING: FillBuffer: curl failed with code 28
15:16:55 T:2956161024 M:1889890304   DEBUG: FillBuffer: Reconnect, (re)try 2
15:16:55 T:2956161024 M:1889886208 WARNING: FillBuffer: curl failed with code 33

winestock Wrote:By the way, I have noticed that in the debug log that it reports "Platform: Mac OS X (10.7.0 i386)". Is there a reason why XBMC reports I am using OS X 10.7.0 when I am actually using OS X 10.6.7?

10.7.0 is the Darwin Kernel version (for OSX 10.6.7) and not the OSX version itself. Try typing uname -a in a terminal and you'll see what I mean. I assume its this that XBMC is logging.