Illustrator crashes when trying to batch save as a pdf with actions

Forum|Forum|7 years ago
February 7, 2019
4 replies
1652 views

I'm running Illustrator CC 2019 on an iMac (macOS: Mojave Version 10.14.3, Processor: 3.2 GHz Intel Core i5, Memory: 16 GB 1867 MHz DDR3, Graphics: AMD Radeon R9 M380 2048 MB) with two external Samsung monitors

I've been using a Batch Actions command to save multiple files (either AI or EPS) as a PDF for the past 9 months and it's been working just fine. All of a sudden when I try to do it now (started happening yesterday), Illustrator crashes every time I try to prefer the action. Below are the steps I take when trying to preform the action:

I select the action I want to preform
Source: Folder
Choose the source folder
Destination: Folder
Choose the destination folder
- Select Override Action "Save" Commands
Errors: Stop for Errors
Hit OK

As soon as I hit OK, Illustrator crashes. This is a necessity for my job so if anyone knows the answer it would be greatly appreciated!

This topic has been closed for replies.

Correct answer ryan-sierrabg

I ended up figuring it out. There must have been something wrong with the action itself, because when I deleted the action and re-created it it started working just fine again.

C

Crittle1

Participant

Illutrator 2022 crashes when I create an action with the "save and close" inside the action, then on the batch choose destination "save and close". Switching to "none" on the batch destination also prevents the crash.

C

Catalin5EA5

Participant

I faced the same problem. Configured an action with open, save as EPS, close, and Illustrator continued to crash everytime I attempted to run it (restart, reinstall, reopen, tried everything). The Crittle1 solution (eliminate "save and close" from the action and just rely on the batch action to do it, well... worked like 1 in 3 attempts. Inconsistent, even for a bug...). So you may want to play with that and see when/where you get the results you want.

ryan-sierrabgAuthorCorrect answer

Participant

I ended up figuring it out. There must have been something wrong with the action itself, because when I deleted the action and re-created it it started working just fine again.