...I did look at the logs but can't make much of them. I looked up some of it and according to the articles I found, this points to faults in the code. But I think that there may be something with my Macbook, even if it only crops up in combination with Sooloos...
Actually sigabrt is usually raised by the code in response to a condition that it cannot handle. Rather than being a fault in the code, its typically an indication that the code has encountered an error condition that it cannot gracefully handle. So the true fault will often still lay outside the code.
Why don't you post a few (10-20 lines) more lines of the stack dump. It may just give more of a clue what the code is trying to handle and if one (ie Meridian - you never know what their coders get up to on their tea break) had inside knowledge of the code, one should pretty much be able to pin point the exact conditions that were not being fulfilled.
Meridian owner since 1992 Prime & PSU, Focal Elear headphones, Roon (ROCK 8Gi5 NUC), Explorer 1 & 2, F80. 200/203, various Sonos (via Roon).
Back after looking into upgrading from Snow Leopard to Mountain Lion I found too many negatives to it, rendering it a non-option. As this is not an Apple forum I will withold further comments.
If anyone has further ideas on how to get Soolooshelper and Synccompanion installed, I'm all ears!
Rowland Model6/BPS6, Rowland Coherence II, Levinson 390S and 37, AudioAanZee Reference Flow music server, Rowland Aeris DAC, Rowland Cadence phono stage, Pass Labs Xono phono stage, Yamaha PX-2 and Thorens TD 160MKII, Transparent Ultra and Reference cables, Apogee Diva magnetostatics (refurbished).
Here's the error report that appears after trying to launch Control:Mac. (the app actually seems to install correctly, the absence of Soolooshelper and SyncCompanion notwithstanding, and only crashes upon launch.)
Here's the first part, up to the lengthy Binary images section:
Date/Time: 2012-10-22 21:44:40.004 +0200 OS Version: Mac OS X 10.6.8 (10K549) Report Version: 6
Interval Since Last Report: 115184 sec Crashes Since Last Report: 33 Per-App Crashes Since Last Report: -21 Anonymous UUID: 8BDB7FDC-0DBB-4370-B6B4-E49C1611B538
Meridian use a third party open source framework called Mono to allow Control:Mac and Control:PC to be developed using common source code. I dont know much about Mono, but it looks from the stack dump that the error is occurring in the early stages of Mono initialising, possibly in areas where Meridian have very little control. My guess though would be that its far earlier than any networking code so networking issues like firewalls are probably red herrings.
I can't help any further other than to suggest that if you have another app that may use the Mono framework, try deleting it. I don't know how Mono is installed and whether it is linked directly to the app, but if the frameworks are shared between apps, there is the chance that there is a conflict between different versions of Mono. I realise that you probably don't know what other apps may use Mono, but if you have any other apps that have a Windows version that looks and feel similar to its Mac version, then it may have been developed using Mono. Likewise, if you have any system files that clearly relate to mono, try also deleting those.
If you like digging deeper, try the section on wapi for starters as it looks to be involved in the crash.
Meridian owner since 1992 Prime & PSU, Focal Elear headphones, Roon (ROCK 8Gi5 NUC), Explorer 1 & 2, F80. 200/203, various Sonos (via Roon).
I do have X11 installed and I do recall an issue I had with the Linn Klimax DS and for which I installed something that could well have been mono... bells are a-ringing but I can't see them clearly just yet;-) I'll dig on, thanks!
Rowland Model6/BPS6, Rowland Coherence II, Levinson 390S and 37, AudioAanZee Reference Flow music server, Rowland Aeris DAC, Rowland Cadence phono stage, Pass Labs Xono phono stage, Yamaha PX-2 and Thorens TD 160MKII, Transparent Ultra and Reference cables, Apogee Diva magnetostatics (refurbished).
I just did a quick scan of the Linn release notes and manuals for various products of theirs and they do indeed seem to use Mono for some of their cross platform software. So it probably is worth investigating this. On one of their products, they specifically mention a Mono conflict with a third party app resulting in their launch icon bouncing then disappearing and the app going no further. Sound familiar?
Meridian owner since 1992 Prime & PSU, Focal Elear headphones, Roon (ROCK 8Gi5 NUC), Explorer 1 & 2, F80. 200/203, various Sonos (via Roon).
Mono is the open-source implementation of the Microsoft .Net framework, which allows .Net apps to run on non-MS OSes. It's just been upgraded to v3.0
It looks from the dump that the Mono library is causing the crash ... the obvious next step would be to try and update the Mono installation separately, in the hope that a later version of the libraries would resolve the issue.
However this could become a slippery slope of OS dependencies and command-line jiujitsu, given that CP would be trying to run the latest Mono version on a relatively older version of MacOS. Personally I'd give it a whirl, but only after I'd taken a complete image of my Macbook to an external hard drive so I could restore it back if it all went pear-shaped. SuperDuper is the recommended tool for imaging/restoring the drive.
HTH.
Last edited by Carl; 2012-10-2309:48. Reason: Long URL replaced with URL tag and description.
Office: MacMini + Roon -> MS600 -> AR LS-9 -> M60s (1993 vintage) Home: [AppleTV -> HD621] + [Roon -> 218] -> G65 -> DSP5200HC + DSP5200s + DSP3200s Being a JAFA in Auckland, New Zealand
Thanks Kent and Ian, I just did a few things. First I installed Mono on top of what had already been installed. That went fine, but it didn't change the behaviour of Control:Mac. Then I decided to get rid of all traces of both Mono and X11. So I dig some Googling and found a script to enter into the command line for removing Mono. X11 was easier to remove thanks to AppCleaner. After that I restarted the computer and repaired permissions. Alas: same result.
Just in case someone is still willing to dig through this, below is the new problem report up to the Binary Images section. For me though, this is it for the Mac, and I will just get my Windows machine replaced. Thanks everyone thus far!
It's pretty much the same crash. Presumably once you uninstalled Mono, you uninstalled Control:Mac, restarted, then reinstalled Control:Mac?
I'm very new to macs but I thought that mine (came with Lion) had X11 as part of the standard OS install. I also don't think it's anything to do with the problem so personally would not touch that.
Meridian owner since 1992 Prime & PSU, Focal Elear headphones, Roon (ROCK 8Gi5 NUC), Explorer 1 & 2, F80. 200/203, various Sonos (via Roon).
Indeed, after deinstalling X11 and Mono, I completely removed Control:Mac using AppCleaner and then reinstalled it the usual way. At some point I'll reinstall OSX on the Macbook, perhaps then it'll all be ok again. But for now I'll revert to Windows. Thanks again Ian!
Rowland Model6/BPS6, Rowland Coherence II, Levinson 390S and 37, AudioAanZee Reference Flow music server, Rowland Aeris DAC, Rowland Cadence phono stage, Pass Labs Xono phono stage, Yamaha PX-2 and Thorens TD 160MKII, Transparent Ultra and Reference cables, Apogee Diva magnetostatics (refurbished).
I agree with Ian - this looks like the same crash. For my money, I suspect that Mono is looking for a dependency of some kind, not finding it, and then not handling the exception elegantly (read: crashing). From the very diligent re-installations you've done, CP, I don't think the solution will be in Mono, but in the OS.
So if you were going to persist with the Mac, the suggested approach would be to image the current OS to an external hard drive, install a later MacOS version as a fresh install (i.e. don't just upgrade), then install Control:Mac and restore user data from the external drive. Of course while this will be excellent in terms of diagnosing the software, it does require an OS change and all the drama that brings. So reverting to Windows looks like a sensible step in the meantime!
Office: MacMini + Roon -> MS600 -> AR LS-9 -> M60s (1993 vintage) Home: [AppleTV -> HD621] + [Roon -> 218] -> G65 -> DSP5200HC + DSP5200s + DSP3200s Being a JAFA in Auckland, New Zealand
Google Search
|
Meridian Systems
|
Meridian Streaming
|
Restaurant
|
WiKi
|
Duncan's Meridian Info
|
Board Rules
|
Restaurant Rules
