unknown sigsegv code 0

[jamie_hurt@adobeforums.com]

Recently (yesterday) everytime I launch Adobe Acrobat 9 Pro, OR Adobe Acrobat Reader 9 - my system becomes unresponsive and hangs. A single CPU (1 out of 4) clocks in at 100% on my Quad 2.66 GHz processor with 8 GB of RAM.

In Apple's Console, the following new error message is suspect as it is consistently getting ping'd twice, every 20 seconds. And is directly related to the launch of Adobe Acrobat services/features.

kernel unknown SIGSEGV code 0

I've tried the basic Adobe recommended uninstall/reinstall procedure, but nothing changes.
In those steps, I've removed the auto Login applications.

My testing so far is not quite on a virgin system, but how far do I have to go to get a modern product like adobe acrobat 9 pro to work on a Mac running Leopard with plenty of hardware capabilities.

-- NOTABLY -- With Adobe Acrobat Pro 9 or Adobe Acrobat Reader 9 open and
a single CPU is getting crushed, IF I also load a PDF via Safari another
CPU (2 out of 4) gets smashed. Of course, I know that's not a good idea,
but the relationship to the viewing technology or back-end communications
to the Adobe mothership are the technical and logical suspects.

Frozen. Locked up. Viewing PDF files with Adobe Acrobat Pro 9 or Adobe Acrobat Reader 9 is 100% useless now.

Adobe your Killing me. Killing me.

Any advice or shared experiences/findings welcome.

As luck would have it, I have a project due that depended on this technology to just work. AND I just paid my 18 month Adobe Tax and purchased the upgrade for the Adobe CS4 Master Collection...Of course, I won't install it until the other shoe drops. any Adobe Dot.0 software release is still very nearly a beta version and users become the testers. Sad but true.

Cheers, Jamie

[John__Justin__Noel@adobeforums.com]

Jamie, I'm having this problem too. I understand it's related to the Adobe licensing manager process and their overly paranoid calls back to the mothership. As usual we the paying customer are penalized for their problems and angst over making a buck.

There is a process viewable by running Activity Monitor you can abort called 'FNPLicensing Serv' after you have launched Acrobat that may, as a quick fix, resolve some issues for you.

I've tried this and Acrobat is not affected as far as I can tell. But none the less it is a huge pain. Guess we are on our own here. When it comes to issues revolving around Adobe's licensing technology you will get no sympathy from them (or support for that matter).

While I MUST use it from time to time if there is a way I can avoid using the Adobe PDF technology I do and use MacOS Preview instead. Adobe has gotten to be a very unfriendly company for Macs recently. Sorry for the commentary... I can't help it. Very bitter here for spending so much money on something that is so riddled with issues and install complexity.

[John__Justin__Noel@adobeforums.com]

PS, if you do get support from Adobe on a resolution on the issue please post it here for the rest of us. I'm not going to spend my day trying to get up with them on it and wading thru the checklist-based tier zero folks in India.

- Justin :O)

[Rick_Baumhauer@adobeforums.com]

This isn't just Acrobat - Photoshop CS4 generates the same message (over and over....) as long as it's running. Fortunately, it doesn't seem to actually impact the system in a meaningful way - no core lockups, etc. Just the log filling up.

[Allen_Oser@adobeforums.com]

I am having this problem as well. It occurs in a similar fashion on both my MacPro and MacBook Pro installations of Acrobat Pro and Photoshop CS4. I think this problem may be associated with my Macpro locking up after about a few days of this (occuring without my realizing it).

I wonder if this is an isolated occurance or is happening more widely. If I hadn't gone to /Applications/Utilities/Console -- "All Messages", I would not have been aware of this issue.

I sent a support request and was directed to (with kind of a generic reply):

<http://www.adobe.com/go/kb404895>

with the suggestion to try solutions 10, 7, 9, and 13 from that document. Tried them, with no luck.

[John__Justin__Noel@adobeforums.com]

About the same thing happening with PhotoShop: It does NOT happen with PhotoShop for me. When I start PhotoShop the 'FNPLicensing Serv' process starts, logs its call home and then is as quiet as a church mouse. But with Acrobat ANOTHER 'FNPLicensing Serv' process starts and that one flagellates the log until I kill the 'FNPLicensing Serv' process created by Acrobat.

I've done software development for years now and I know how difficult it can be to keep a complex piece of software afloat. Adobe has my sympathy there. But the entire CS suite (any version you want to talk about) just has the feel of a house of cards kept together by spit, luck, fair weather, and hope. We use it because we MUST. Maybe the MUST part of that will change one day... that would be nice. Cause I don't think Adobe's ways are going to change. I'm resigned to marginal interest and support of their product. And that's OK.