Illustrator CS crashing...any solution yet?

[Susan_Cooper@adobeforums.com]

I agree with Christian and YP Tang! What is a "Haxie" any way and why should we have to
go looking all over the system for this or that file to delete it and still not see illustrator CS run. Adobe needs to fix this ASAP!

[Christian_Semmel@adobeforums.com]

I do have a very general suggestion that one of my users gave me. When saving Illustrator files uncheck the pdf compatability box. This greatly reduces save times and decreases file sizes significantly. It is a problem if you plan on taking your Illustrator files into Photoshop or InDesign later. But you can always resave the file with pdf compatibility if necessary.

[Wade_Zimmerman@adobeforums.com]

Why would it affect AI CS and not 10. Simple they are different and may be affected because the features or general code of AI CS has changed a lot and there fore the two versions are very different hence it would be not at all strange that a haxie or a font or another app would conflict with AI CS and not AI 10.

Can you see the logic in that?

A haxie is software that i order to function has to alter the system and because of this it can easily conflict the code of AI CS if it interferes with any part of AI CS that also
interacts with that aspect of the system. Especially if it is always running.

Corrupt fonts can do this as well and yes it can affect one without affecting the other.

Also system and software updates and documents and naming of documents can even effect this.

As to your complaint that you sort of don't think it is you and that you think it is AI CS
you might be a small group that is genuinely affected by some issue but for most people it seems to function well. That might actually lead you to suspect yourself that perhaps my system is either not been maintain properly that I did not the fundamental task required to keep the system running smoothly etc.

If you have to ask what those steps are then you haven't been doing them.

You might want to read some of the other posts where the user found out after a while…Oh, yes it was this application or that haxie or that font that was causing the problem after all!

I am not going to say it will help all of you but perhaps it will help one or two of you.

[Dee Holmes]

I still don't understand "haxie". Can anyone give more examples? It's just not like a 3rd party program, right?

[Wade_Zimmerman@adobeforums.com]

That is sort of correct. Alias Menu would be a Haxie, Moon Menu, File Buddy (I think),
With Stuff it Deluxe Magic Menu would be a Haxie.

[YP Tang]

Wade,

Granted that there are certain issues which are causing AICS to crash on certain people's machines...but there are also people here who are running clean systems who are also experiencing crashes.

I downgraded two G5s today (reformatted & reinstalled) to 10.3.2 and ran one with FontBook and the other with SuitCaseX1...because some people were saying that Suitcase might be an issue...well...guess what...on BOTH systems, AICS crashed AGAIN! If it is a font conflict issue, why doesn't Quark crash, or MS Word, or MS Excel or Photoshop CS...need I go on?... sorry...but it's been terribly frustrating and I'm not even the user who has to meet deadlines with AICS!

[Andrew_Colfelt@adobeforums.com]

Mismatched RAM pairs was the culprit in my case.

Apple RAM + Super-Duper Hyper-Expensive Ultra-Low-Latency aftermarket RAM = BAD

Apple RAM alone = GOOD

SDHEULL aftermarket RAM alone = GOOD

[bethfullen@adobeforums.com]

I have been having a problem with illustrator and quark crashing. Illustrator seems to crash when I save as a CS EPS file and Quark is not letting me import Illustrator EPS files into it. i can import TIFF's from Illustrator, but not EPS. It crashes everytime I bring an EPS file in, even older version ones. We are trying to get our IT guy to help.

[Wade_Zimmerman@adobeforums.com]

Beth use a tiff preview for the Illustrator eps files and not the Mac Pict Preview.

Tang I'll apologize in advance for not having patience with someone like your self.

I explained it to you why a conflict with one program because of corruption may affect one program and not effect many others. It common sense to realize that if there is some about the corruption of the font that has cause code to be written or deleted then such recreated code could be in conflict with the code of one specific
application unless it is effecting the system.

It doesn't really take a rocket scientist to figure this out.

Maybe this will illustrate this for you better, you have an appliance that you plug in to a certain outlet that outlet shorts out when you use a certain appliance because there is a slightly loose wire in the outlet and this appliance uses more current than the other appliances that you usually would use this outlet with. The reason because it uses more electricity it heats the wires more expanding it enough for the the loose strand to touch other metal. OK it shorted out you change the fuse and you plug in another appliance and it works fine.

So there must be something wrong with?

A. The Appliance
B. The Fuse Box
C. The Outlet
D. Trouble Shooting Is a Good Way to Determine the Source
E. You are one lazy person and will never solve your problem
because you are too much in love with your problems.

[YP Tang]

Wade, You can apologise all you want but that doesn't help me or anyone else.

If you can't offer any assistance towards solving a very genuine problem that myself and a lot others too are experiencing, then perhaps you should just shut up and go bother someone else.

Don't insult me by saying that I'm too lazy to solve my problem. Coming to this forum or any other forum for any issues is always a last resort..for me anyways. Did you not think that we've tried to rule out other issues before coming in here and hoping to get assistance to a very frustrating issue which is very real for us.

To say that "SORRY there's no problem becoz it's not happening to me"...is a very selfish attitute indeed.

[Joe_leMonnier@adobeforums.com]

Whoa! back a bit to Andrew's posting... mismatched pairs of memory.
I too am blessed with some third party memory, but it is only Illustrator that crashes on my machine (dual G4). Both 10.0.3 and CS crash on occasion. Version 10 will crash when saving a file as EPS, while CS seems to just slow down , stutter, and then quit in screen redraw or sometimes with a mouse movement. I've posted this before, so it must be alittle boring, but I've somethig new to add. Are you still with me here (Wade?).

For the last 3 or 4 days of constant Illustrator use I have had no problems at all-even while working on some of the same files that previously would crash up to 3 times daily. Nothing new has been installed or changed except for quite a few keyboard shortcuts and a Virex update ( last Friday). Does this write a new prefs file? So far my experience has been that it took about two weeks for the crashes to occur (to a reinstalled clean disk) so I expect them to return soon.

So, to return to the memory issue: Is this a known problem? Only on illustrator (both 10 and 11) is it an OSX issue? Is it an issue with only the later versions of OSX? (my third party memory is about 10.1 vintage)

[Wade_Zimmerman@adobeforums.com]

Tang you did read what I wrote and that is how I know you are lazy and you probably always blame other people for your problems. Beside s i have no more time if you can't see the logic of what was written.

Hi Joe,

The RAM issue has popped up a couple of times and I had suggested it a few times as well. On OS 10.3.3 and even with the initial 10.3 install of Panther there showed showed issues with mismatch RAM. This could a a problem with the update to the firmware required for the Panther install or simply with Panther.

The Question that always arises is that why does it only affect AI CS in this forum, in the Photoshop forum you will get similar queries asking why does it only affect Photoshop and in the ID forum and Go Live Forum the same thing.

The answer is as I illustrated in my previous post because the problem only shows up when you use a function that manifests the crash by activating the weakness in the RAM configuration, if you don't happen to do this because of the way you work you might not notice it at all since your computer will not crash. That does not make things OK as it might cause you problems in the future. So you either want to get rid of the RAM or hope that Apple not Adobe changes its policy on the use of mismatched RAM and or allows for the USe of on Apple RAM.

If Apple is deliberately doing this it stinks but at any rate the RAM manufacturers should jump in and create software that will overcome Apples shortcomings or policy or not sell the RAM.

I would Remove the third party RAM and work with the computer for three weeks if all is well I would then reinstall the third party RAM and see what happens if after a week or two it starts crashing again, I would be mad as hell and either ask the manufacturer for RAM that will work or get my money back as RAM is guaranteed for life.

I hope this helps, even Tang, though I suspect you would not understand.

[Joe_leMonnier@adobeforums.com]

The problem, may be easier to live with than running with only 512 MGs of RAM.
Its funny how it comes and goes though.

[Wade_Zimmerman@adobeforums.com]

Well if you fid it is the RAM you will be able to get your Money back and find out what type of RAM will work well by making a post here or in the Apple forum.

But you did just demonstrate the kind of thinking that perpetuates the problem and of course this is someone else's doing and why doesn't Adobe figure out how to solve a problem they of course have no control over and is something you can fix.

I have to admit I don't see the sense in it.

I have a colleague who is an intelligent professional who was having problems with out putting to his Fujix I think that is how you spell it from images he scanned from 4x5 negs on his Mircotech scanner so I offered to let him come to my place and try it with my Epson 3200. He was seeing grain on the prints. We opened his scanned files in Photoshop and we could see the grain or noise actually. So I scanned the image on my Epson from the same neg. And there was clearly no such problem.

Now my colleague has a problem overcoming a certain understanding and belief he has that just because there is no glass between the neg and the sensor in his scanner and there is one on mind that his scanner should do better than the Epson.

He is now rationalizing that he has his scanner to close to the monitor or some other phenomenon is causing this even though before he came to my place I explained to him that I have never work with a Microtech scanner in which I did not see noise.

He one has a output device that is clearly not as good as Digital C printer that he has gotten much better result from from the same file and his scanner is equally faulty.

Let me ask you Joe and Yang how do you convince someone that it is within them were the actual problem lies and the exterior causes are consequential only?

You can fix this if you want, but it does not appear you want to.

I find it kind of interesting and actually you have both been helpful to me in solving a problem that I have and so I thank you for being you. My colleague helped as well!

Have a nice day!

[Joe_leMonnier@adobeforums.com]

Wade, please, I don't think I said that at all. I don't plan to get my money back for 4-year old RAM that was designed for OSX10.1 and I don't blame anyone. I accept your explanation of why it may only happen to Illustrator but then again I don't known where the problem lies. That it only happens to Illustrator (on MY machine) does not point the blame at Adobe, or at least wasn't intended to.

I post on the forum in the hope that somehow I or someone else will find solutions by recognizing similar situations. It is not to point blame. believe me, I would like to but there appear to be only a couple of dozen people having this particular problem. In this I diagree with Tang a little in that it doesn't seen that illustrator is that problematic except on some people's machines (mine included). We would all like to known if there is something we (or Adobe) can do to correct it. My guess is that it's a relatively rare problem but this is no consolation for those who have it.

As for the memory, it seems a possible solution except I would have to replace the flawed memory and for the money it would cost, I would probably rather live with the occaisional crash. It would of course be nice to know whether this is the cause, but i haven't the time to experiment; sorry.

[Wade_Zimmerman@adobeforums.com]

I didn't actually mean it that way I appreciate your problem and some how I think this will right itself with future updated from Apple. And I know that you recognize that
the can be difficult.

Also you actually answered my question wen I asked why you would continue on your corse as is withy quite good answer, one that makes sense you have the RAM for quite a while and perhaps this is not for some reason the right time to do anything about this.

I think by getting to this point so that the complete picture of what your system is all about might also relate to some other user who as found the solution or a solution to the problem.

[Lorena_Andreoni@adobeforums.com]

YP Tang I think you are right.

I have been struggling with AI CS from the beginning: I have bought a new G5 (1.8 DP Panther 3.0 Gb ram) and the new software package "Creative Suite Premium", I have simply installed the package so there are no absolutely "haxies" or different fonts or something else strange ... but AI CS is slow and "quits unexpectedly" very often ...
maybe it could also be a problem with my configuration, but honestly I am rather surprized to discover AI CS does not work under such standard conditions ...

I really hope there will be a patch soon, as at the moment the situation is disappointing!