O$: Stability of Studio 6.0 on Mac OSX?
Bastiaan Olij
bastiaan at basenlily.me
Thu Dec 4 15:41:59 EST 2014
Hey Paul,
First off, make sure you are using 6.0.3, we did have issues with 6.0.1.
That said, up until a month ago I worked on 10.8.5 with very few issues
on Studio 6. My colleague however was plagued by unexplained crashes for
months, anything from debugging through reports, working with the VCS,
opening the method editor at the wrong moment. Initially on 10.6, she
later upgraded to 10.9 hoping that would fix it as 10.6 isn't officially
supported by Studio any more, with no improvement.
The problems didn't go away until we did a clean install of Mac OS X on
her machine. That is the only difference between our two machines, mine
came with 10.8 when it was bought, hers went through a number of
upgrades. There must be something brought over from the older OS that
Omnis didn't like.
Cheers,
Bas
On 4/12/2014 1:53 pm, Paul Mulroney wrote:
> Hi $All,
>
> I'm upgrading one of our clients from Studio 4.x to Studio 6.0, and I'm noticing that Studio 6 is crashing very frequently on me in development mode. Three times this morning!
>
> I'm developing on a Macbook running Mac OSX 10.8.5.
>
> Each crash is the same:
>
> Crashed Thread: 19 Dispatch queue: TFSVolumeInfo::GetSyncGCDQueue
>
> Exception Type: EXC_BAD_ACCESS (SIGBUS)
> Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000fefff000
>
> GCDQueue is "Grand Central Dispatch" - a technology developed by Apple to optimize application support for systems with multi-core processors and other symmetric multiprocessing systems. It is an implementation of task parallelism based on the thread pool pattern. (To quote wikipedia)
>
> This may or may not be an Omnis issue, but how can I help narrow down the cause of crashing?
>
> By contrast, Studio 5.2.2 has crashed twice in the last two months, both times related to Java.
>
> Is anyone else having stability issues? I'd like to spend my time actually programming rather than restarting the app every 10 minutes ...
>
> Regards,
> Paul.
>
>
More information about the omnisdev-en
mailing list