[mikeSiLVO]

Not sure this will be any help, but I took a look at the crashing issues as far as my time and lack-of-skinning-skill allow. I was able to reproduce a crash with a small amount of consistently (maybe 1/3rd of the time) from the main menu to music by first letting the system idle for a couple of minutes. Looking in the log, and looking at the on-screen debugging (enabled via addon.xml - the xbmc.gui.skin <extension />), it shows the home.xml is being deinit'ed, but mymusicnav.xml isn't being init'ed, and the on-screen debugging still shows home.xml. To my mind, that suggests that the issue is happening most likely on unloading the home.xml file.

The only thing that stands out to me on closing the home.xml is the CancelAlarm calls on <unload /> - I've seen elsewhere on the forums that there are some issues with AlarmClocks on Jarvis (here). After commenting out the CancelAlarms I haven't been able to reproduce the crash with a couple of dozen tries. Could well be coincidence, and if it is an issue it may not explain all the crashes and is likely to be a difficult issue to code around (and may be too late in the release cycle for any potential issue with AlarmClocks to be fixed in core, if indeed there are any issues and if the team are aware of them.) But it might give another avenue to explore

(For the record, this is on an old Mac Mini - 2009 I think - which I believe has Nvidia graphics, with a remote SQL library.

I am literally working on the home.xml right now Was toying with scrapping it altogether and using skinshortcuts... Not sure if I want to start that with my current situation though It looks like they are just there to scroll the widgets and hometiles (I have no idea what a hometile is )...