It's an implementation detail of pthread_cond_wait (which waits on the condition variable). I think in reality it is not using any CPU, but observatory profiler is sending signals to the waiting thread (because it does not know that waiting thread is not doing any actual work). /cc @r...
With the cc cleaner tool, I did uninstall the core-sync tool, rebooted and opened cc. Did not update anything with Acrobat Pro. Manually running software updates via cc does not change Acrobat Pro. Do I keep working with the cc cleaner tool or xml file maybe? I have not tried running...
Pthread_cond_wait now acts like Linux and BSD: Resume waiting for the condition variable as if it was not interrupted, rather than returning 0. The internal <sys/_locale.h> header was renamed to <xlocale.h> for source compatibility with other systems. Try harder supporting Netapp drives. W...
/* on Windows, writing to the argv does not hide the argument in process lists so it can just be skipped */ (void)argc; (void)argv; return 1; #else (void)argc; argv[0][0] = ' '; return (argv[0][0] == ' ')?0:1; ...
With the cc cleaner tool, I did uninstall the core-sync tool, rebooted and opened cc. Did not update anything with Acrobat Pro. Manually running software updates via cc does not change Acrobat Pro. Do I keep working with the cc cleaner tool or xml file maybe? I have not tried running...
With the cc cleaner tool, I did uninstall the core-sync tool, rebooted and opened cc. Did not update anything with Acrobat Pro. Manually running software updates via cc does not change Acrobat Pro. Do I keep working with the cc cleaner tool or xml file maybe? I have not tried running...