Kodi Community Forum - Mountain Lion w/ XBMC Eden two issues

I am working on a MacBook Pro w/ Retina Display running Mountain Lion (Mac OS X 10.8). I am having two separate issues with it, which I haven't been able to locate any solutions to as of yet. So, I now post this thread and hope someone is able to provide some sort of solution to my issues.

1.) When XBMC starts up I often get a message about having to "reopen" the application. I have the option to "Reopen" or "Don't reopen" and XBMC starts up when I select one of these - but it is not static. Sometimes I have to select "Don't reopen" and sometimes I have to select "Reopen" to make the application start up. Kind of a 50/50 quiz show builtin to the application. When the application starts I have no trouble using it so far - no crashes or weird hangups or anything.

2.) When i have XBMC opened on (let's say) desktop 3, and while idling in the menus I swipe to desktop 1 and read up on a forum or something, I notice the CPU usage for the application shoots up from 4-6% to 30-50% in the activity monitor. I have fiddle about with this, making sure I could reproduce the issue, and indeed it is EVERY time I change away from the desktop running XBMC the CPU usage instantly shoots up.

I have supplied a paste of xbmc.log from a startup where both issues were present. http://pastebin.com/9uxzuyhi

If you need anymore information to help me solve the issue please don't hesitate to comment on it and I will do my best to supply any information necessary.

Thanks

1. Sounds like the GateKeeper feature of ML. In ML only signed apps from the AppStore are allowed to be started normally. XBMC is not a signed app (because we don't own a proper certificate for that). So you have to allow all Applications in Systemsettings->Security->Gatekeeper - see http://www.macrumors.com/2012/02/16/os-x...y-default/ - but it is only a guess - because i have never seen such a dialog. (if gatekeeper isn't the issue please post a screenshot of the message).

2. Read up dirty region in our wiki http://wiki.xbmc.org/index.php?title=Dirty_regions

Hi, Memphiz

None of the above seems spot on, I'm afraid. The Gatekeeper is set to allow all applications at the moment - I hit that snag on the new OS quite quickly. I have supplied screenshots of the error I receive from time to time.

http://imgur.com/gAgos&omBBJ
http://imgur.com/gAgos&omBBJ#1

The dirty region did nothing for my CPU usage at all. Except, now I can hear a faint noise from the machine when it updates - maybe it was there before too I just didn't notice it, but it sounds a bit like my old Asus motherboard that had some coilwhine when writing to memory. Only when on another desktop and the XBMC application is opened though.

click the "report" button and post the complete crashlog on pastebin.com and put the link in here.

I got the report right here: http://pastebin.com/yG3xvbRU

Could it be an issue with the Retina display Macbook Pro model perhaps Huh

Could you also post a xbmc.log (not sure if one gets generated because the crash is very early). Well of course it can be due to the retina display. But normally apple should hold this special stuff away from us coders and it "should" just work without us doing anything special *grrr*.

Ohh i saw that davilla fixed that crash. Please try the nightly build tomorrow and see how it behaves.

Hi legenderry,

i can relate to your problem #2.
but this is not a problem with mountain lion. this happend with lion and snow leopard too.
as soon as you switch desktops, or when you switch from full screen to windowed mode and than switch the desktop the cpu/gpu usage increases drastically.

<gui>
<algorithmdirtyregions>1</algorithmdirtyregions>
<nofliptimeout>1000</nofliptimeout>
</gui>

added this in my advancedsettings.xml got the cpu usage to 5% when swtiching desktops. Just be sure xbmc is idle (no video playing or so - just sitting somwhere in a menu). See "dirty regions" in the wiki again. If you are sitting in the main menu be sure to turn off the news ticker. Also the debugging printouts may lead to excessive rendering/cpu increase when in background.