Compressor 4.1.1 crashes when trying to create custom setting from scratch

Question

Craig Seeman Author

Level 4

2,137 points

Compressor 4.1.1 crashes when trying to create custom setting from scratch

OS 10.9.2 (and was the same with 10.9.1)

Compressor 4.1.1

Clicking on "+" New Setting caused an immediate crash.

Tested in TWO User Admin accounts so it seems Systme, not User related.

Also ran Digitial Rebelion Compressor Repair 2.2.7 and that also didn't fix the issue.

Permissions had also been repaired.

Key part of Crash Log show Crash on Thread 0 and shows Apple Foundation and Apple ProKit very high up. It continues on repeating as you see it.

System is MacPro 2008 8 Core.

Any Suggestion (again noting that this system System and not User specific).

Process: Compressor [1486]

Path: /Applications/Compressor.app/Contents/MacOS/Compressor

Identifier: com.apple.Compressor

Version: 4.1.1 (242175)

Build Info: Compressor-24217005037000000~1

App Item ID: 424390742

App External ID: 360972635

Code Type: X86 (Native)

Parent Process: launchd [346]

Responsible: Compressor [1486]

User ID: 501

Date/Time: 2014-02-25 15:38:16.104 -0500

OS Version: Mac OS X 10.9.2 (13C64)

Report Version: 11

Anonymous UUID: E87C08D8-0851-D565-515D-E7E41CC843DC

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000bf72fffc

VM Regions Near 0xbf72fffc:

Stack 00000000b1064000-00000000b10e5000 [ 516K] rw-/rwx SM=COW

--> Stack 00000000bbf30000-00000000bf730000 [ 56.0M] ---/rwx SM=NUL

Stack 00000000bf730000-00000000bff30000 [ 8192K] rw-/rwx SM=PRV

Application Specific Information:

Performing @selector(newSetting:) from sender NSMenuItem 0x7b56eed0

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

0 libsystem_pthread.dylib 0x93081643 __mtx_droplock + 488

1 libsystem_pthread.dylib 0x93081af9 pthread_mutex_unlock + 83

2 com.apple.Foundation 0x91e9ded3 -[NSLock unlock] + 262

3 com.apple.Foundation 0x91ea46d1 +[NSBundle bundleForClass:] + 779

4 com.apple.prokit 0x47c03c67 +[NSObject(ProAdditions) isDefinedInBundleForClass:] + 150

5 com.apple.prokit 0x47c03cbd +[NSObject(ProAdditions) isProSubclass] + 62

6 com.apple.prokit 0x47c88ea7 -[NSCell(ProAppearanceExtensions) proSetFont:] + 54

7 com.apple.prokit 0x47c88f46 -[NSCell(ProAppearanceExtensions) proSetFont:] + 213

8 com.apple.prokit 0x47c88f46 -[NSCell(ProAppearanceExtensions) proSetFont:] + 213

9 com.apple.prokit 0x47c88f46 -[NSCell(ProAppearanceExtensions) proSetFont:] + 213

10 com.apple.prokit 0x47c88f46 -[NSCell(ProAppearanceExtensions) proSetFont:] + 213

Posted on Feb 25, 2014 12:48 PM

Reply

Answer 1

Studio X

Level 7

27,229 points

Feb 25, 2014 1:09 PM in response to Craig Seeman

Are all your software updates installed?

If so, the next step would be to use Digital Rebellion's FCS Remover to completely delete Compressor 4 then to restart and reinstall from the app store.

x

Reply

Answer 2

Craig Seeman Author

Level 4

2,137 points

Feb 25, 2014 1:17 PM in response to Studio X

Why ofcourse that was the very next thing I tried. Probably while you were typing your post.

Used FCS Remober 3.0.9. and removed Compressor 4.1.

Rebooted.

Empty trash

Rebooted.

Reinstalled Compressor 4.1.1 form the App Store.

Did not fix the issue.

Thanks for suggesting that but no fix.

Reply

Answer 3

Craig Seeman Author

Level 4

2,137 points

Feb 25, 2014 1:24 PM in response to Studio X

BTW looking at what FCX Remover removes, When selecting Compressor 4 it only removes Application, Preferences, Receipts. Given Core Apple Foundation and ProKit position in the crash log. My hunch it's system related beyond that. Just a hunch.

Reply

Answer 4

Studio X

Level 7

27,229 points

Feb 25, 2014 1:34 PM in response to Craig Seeman

Hence my question regarding ALL software updates. ProKit is a system level thing that should have been picked up if it is out of date when you run Software Update.

One other tack is to create a new user acct with admin privleges and try to run Compressor from that acct.

If it works, it really is a preference issue (which are largely user based).

If it doesn't, it is likely a system level issue.

x

Reply

Answer 5

Craig Seeman Author

Level 4

2,137 points

Feb 25, 2014 1:40 PM in response to Studio X

Yes all updates are current.

My very first tested in my first post was to create a New User Admin account (so all user and app prefs are fresh) and it still crashed when attempting to create a new setting from scratch.

It's Definately system related.

I'll also note that I've tested one of the presets and it encoded without issue.

Reply

Answer 6

Studio X

Level 7

27,229 points

Feb 25, 2014 2:54 PM in response to Craig Seeman

Strange. Not sure what's next other than an erase and reinstall of the system and apps. There must be a less nuclear solution.

Perhaps someone with more experience troubleshooting 4.1 will wander by and offer up a solution.

Sorry,

x

Reply

Answer 7

Russ H

Level 7

22,432 points

Feb 25, 2014 4:38 PM in response to Craig Seeman

I'm not setting myself up as an uber troubleshooter, but you've done all the usual user level fixes I would normally suggest, And if it's system, it seems to me that it would probably be a conflict – perhaps a codec. Do you have Perian installed? FX Factory? Plug-ins (probably)? Try disabling them sequentially?

Also, if you have Digital Rebellion's Pro Maintenance Tools, run the report through their Crash Analyzer.

Russ

Reply

Answer 8

Feb 25, 2014 7:19 PM in response to Craig Seeman

Hi Craig, if you haven't resolved this abend, would you post the FULL DUMP somewhere.. not on in this thread? Some of us can have a look at it for ya. Also the the logs in/near the region / timeof this error from /private/var/log/system.log 😀

Warwick

Hong Kong

Reply

Answer 9

Craig Seeman Author

Level 4

2,137 points

Feb 25, 2014 8:51 PM in response to Studio X

I spoke to Apple and went through everything I've done and I've done all the normal troubleshooting techniques. The senior tech suggested that I create a partition with OS 10.9.2 and Compressor 4.1.1 (or all ProApps) and test to see if the issue is still present. From the crash log it does seem like a low level OS issue.

They handed me off from ProApps to an OS tech to start on the partition but it failed to twice. I'll continue with them tomorrow.

Reply

Answer 10

Craig Seeman Author

Level 4

2,137 points

Feb 25, 2014 9:00 PM in response to Warwick Teale

I tested with current versions of Compressor Repair and FCX Remover (removing Compressor) but neith helped.

Someone also mentioned Crash Analyzer although I didn't see that (first time using Digital Rebellion's tools)

I'll look through System Log as well.

Reply

Answer 11

Feb 25, 2014 11:29 PM in response to Craig Seeman

hmm...Prokit is installed by the OS. Did you happen to run any utility that modifies system files? If you have access to another 10.9.x machine you could probably use rsync and copy /System/Library/PrivateFrameworks/ProKit.framework, but I guess if you have another machine you would already know if its specific to just the one machine. I would think installing to Mavericks to another volume would fix it. Maybe even just install to the second volume, then copy over Prokit then boot back into the original volume and see if the problem persists.

Reply

Answer 12

Russ H

Level 7

22,432 points

Feb 26, 2014 5:39 AM in response to Craig Seeman

Craig Seeman wrote:

Someone also mentioned Crash Analyzer although I didn't see that (first time using Digital Rebellion's tools)

There is a fully functional 15 day trial of PMTavailable and it's been updated for 4.1 and 10.1 support. The Crash Analyzer is included. I'll be very interested in what it says (and what Warwick gleans). Almost everything that's posted here have tended to be user level issues; this clearly seems to be an exception.

Russ

Reply

Answer 13

akwa

Level 1

0 points

Apr 23, 2014 3:14 PM in response to Craig Seeman

Hi Craig

I seem to have the same problem as you. I found out that Compressor 4.1x works after a safe boot, so there must be some sort of software conflict that causes the crash.

Were you able to find a solution by now?

Thanks,

Arnoud Kwant

Reply

Answer 14

Craig Seeman Author

Level 4

2,137 points

Apr 23, 2014 4:34 PM in response to akwa

Arnoud, as a test I created a new boot drive with only FCPX 10.1.1 and Compressor 4.1.1. That worked fine.

I have not been able to solve the problem since it's unlcear what the conflict is. Even if I were to reformat and restore from Time Machine I'd probably end up bringing back the issue.

I called Apple Tech Support, provided system config, crash logs, system log at the time of the crash. They were never able to solve the problem. I'm actually decent at reading crash logs and the crash thread just points back to Apple software. Sheesh. Completely frustrated. 😢

Reply