Hi Matthew -
Could you let me know what e-mail address or private method I can use to send you a link to download a document that is giving me consistent trouble? It is a somewhat proprietary document for a client and I'd rather not post the link in this forum.
I've tried disabling preflight, and also did this, which was recommended to me previous by Adobe support, to no avail:
1. Delete the "Datastore" folder located here:
2. HD / Library / Application Support/ Adobe / SING / Mark II / Datastore
3. Relaunch InDesign and test.
I have an open case number for this issue with Adobe support - it's 181910243. Using the script for exporting a pdf in the foreground is the only method that works for me. Attempting to export an idml of the same document also crashes InDesign, though a homemade Applescript which forces the export in the foreground works:
set this_file to choose file
tell application "Finder" to set file_name to (name of this_file)
set posix_this_file to POSIX path of this_file
set file_name to ReplaceText(file_name, ".indd", ".idml") of me
-- display dialog file_name
tell application "Adobe InDesign CS5"
tell active document
export format InDesign markup to choose file name with prompt "Save IDML Where?" default name file_name default location posix_this_file
on ReplaceText(theString, fString, rString)
set current_Delimiters to text item delimiters of AppleScript
set AppleScript's text item delimiters to fString
set sList to every text item of theString
set AppleScript's text item delimiters to rString
set newString to sList as string
set AppleScript's text item delimiters to current_Delimiters
thank you -
I tried to read the whole thread and it's a hard job :-)
The problem I've been experiencing is a bit different than discussed here but I think it is related though for me it is inherited since CS4.
What I actually need is PDFs with working bookmarks and cross references. One of the reasons to upgrade was the hope that in CS5 if would be better done and more convenient to use, which is unfortunately not exactly the case.
The problem exporting PDF for me is that _some_ of my files do the export up to the very end when pdf should be optimised for web and then pop up the "Cannot generate PDF" error box with no more explanation. I know that optimisation option is what can be switched off to complete pdf creation. That pdf would then open up in acrobat with the TOC page empty and error saying that the page is corrupted.
In my case I found a workaround - recreated the TOC styles, deleted the pages with the old TOC, inserted new pages and generated a new TOC. This helped for the file with reproducible issue.Maybe it helps someone else.
I had an adobe case 0182009446 open for TWO months and twice got a suggestion to _print_ to pdf instead of real export which cannot be a fix for me. So I closed (forced quit) the issue which the support team considered as "resolved".
A file is uploaded to that issue which reproduces the problem on my Win7 64-bit with all updates and ID 7.0.3. Support team stated that they have reproduced the issue as well and suggested to _print_.
Matthew, please take a look at the issue if you're interested and it might help you a bit.
However I have more files from CS4 that from time to time generate the same export problem. Unfortunately I have no CS4 any more and cannot export them in inx as advised here. Creating virgin templates in CS5 and copy/paste into them is a nightmare, though this is the only thing that _might_ help. At least from me it worked for a couple of files already.
I'd love to have a fix either on the ID side or telling me, what is wrong with my masters or styles or whatever can be wrong with the files that i'm creating out of my template, which is consistent for all my documents (technical references and user manuals).
For those of you who are successfully able to export to PDF using the script or Booked document to prevent the background, threaded export, please consider this...
After not being able to reproduce a crash with some of the files I've been provided, I worked with a customer to get a crash log from his background PDF export failure. The crash log appeared to indicate an impact from the Extensis font auto-activation plug-in. If you are using any of the Extensis tools in conjunction with InDesign CS5, and are experience failures to export to PDF in the background, please disable the Extensis toolset, restart InDesign, then try to export again and see if the export is successfull. Please report results here, including the exact Extensis product[s] and version[s].
I loaded the CS5 suite as a clean install on a new computer (Win7, 64 bit) and also installed Extensis Suitcase Fusion 3 (showing version 188.8.131.52). This installed auto activation plugins in several of the CS5 applications, including Indesign. At that point there was very little on the computer: CS5, Suitcase, Office 2010.
Despite assurances from Extensis that the application was 'good', the plugins caused *all* my CS5 applications to crash - actually, they refused to start up - apart from Photoshop 64 bit (the 32 bit installation also failed). Removal of the plugins from all CS5 applications enabled them to start and run properly (ignoring the fact that bits of Indesign don't work as they should, which is the subject of this thread).
In my case, these plugins caused a failure in the software, as opposed to a crash once the software was running. None are now installed, though Suitcase (other than this factor) appears to run correctly.
We use the Universal Type Server 2.1.1 (23).
However, on every Mac in our shop, where people have been having this problem, the moment I disable the flightcheck in InDesign, they have no more problems exporting PDFs. This has been a consistent fix for this.
Obviously, we don't want to be running forever without a preflight being done, but we also don't want to take our shop back to the dark ages of pre-font server.
If I get a moment's breathing room, I will try running this test for you, and see what happens, though, in the interest of providing a solution for all.
He wants you to check if ID is using up all your RAM. If you open it up (it'll be the top app in your utilities folder) and scroll down to ID you should see a number like 2.8 or 5.3 under % of CPU column. Should be a small number. If you're seeing something like 20% or 80% or some really large #, there is a problem somewhere. If you select ID, then hit Sample Process you'll get a readout you can paste here. I have no idea what the info means but someone will.
I've tried updating Universal Type to it's latest version. I've also tried turning it all the way off, and InDesign is still crashing.
But at least I am getting a real crash report now, and if you'd like another file to try out, I've got one here for you.
Process: Adobe InDesign CS5 
Path: /Applications/Adobe InDesign CS5/Adobe InDesign CS5.app/Contents/MacOS/Adobe InDesign CS5
Version: 184.108.40.2065 (7030)
Code Type: X86 (Native)
Parent Process: launchd 
Interval Since Last Report: 685266 sec
Crashes Since Last Report: 171
Per-App Interval Since Last Report: 456761 sec
Per-App Crashes Since Last Report: 17
Date/Time: 2011-04-05 10:52:16.503 -0500
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: CC909394-8DB6-49DB-BAD9-3ABDACAC03B1
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 com.adobe.InDesign.Text 0x1df95fce GetPlugIn + 1096990
1 PublicLib.dylib 0x016f3905 VOS_SavedData::Normalize() + 501
2 com.adobe.InDesign.Text 0x1df9fe93 GetPlugIn + 1137635
3 com.adobe.InDesign.Text 0x1e0b3469 GetPlugIn + 2265529
4 com.adobe.InDesign.Text 0x1e0c8927 GetPlugIn + 2352759
5 com.adobe.InDesign.Text 0x1e0c8f31 GetPlugIn + 2354305
6 com.adobe.InDesign.Text 0x1df7e161 GetPlugIn + 999089
7 com.adobe.InDesign.Text 0x1df7eabf GetPlugIn + 1001487
8 PublicLib.dylib 0x014d9482 Command::DoImmediate(short) + 34
9 com.adobe.InDesign.Utilities 0x1a818aa3 0x1a817000 + 6819
10 com.adobe.InDesign.Utilities 0x1a818ccc 0x1a817000 + 7372
11 ...adobe.InDesign.AppFramework 0x19482788 0x19468000 + 108424
12 PublicLib.dylib 0x014da5db CmdUtils::ProcessCommand(ICommand*) + 59
13 com.adobe.InDesign.SlugCubed 0x23cf81fd TTTextUtils::CopyStoryRange(ITextModel*, RangeData const&, ITextModel*, RangeData const&) + 637
14 com.adobe.InDesign.SlugCubed 0x23d1461a SlugMechMetaDataClientNotify::InitializeSlugTextFromStyleLayout(UIDList const&, UIDList const&, PMReal const&) + 394
15 com.adobe.InDesign.SlugCubed 0x23d1512b SlugMechMetaDataClientNotify::DoUpdateSlugText(ISlugDocDataMgr*, UIDRef const&, IDAAttributeGroup*, SlugInstance&, IMechMetaDataMap*, IMechMetaDataMap*) + 2731
16 com.adobe.InDesign.SlugCubed 0x23d15877 SlugMechMetaDataClientNotify::UpdateSlugText(ISlugDocDataMgr*, UIDRef const&, IDAAttributeGroup*, SlugInstance&, IMechMetaDataMap*, IMechMetaDataMap*) + 215
17 com.adobe.InDesign.SlugCubed 0x23d15a27 SlugMechMetaDataClientNotify::HandleSlugContentUpdate(UIDRef const&, IDAAttributeGroup*, IMechMetaDataMap*, IMechMetaDataMap*, IMechMetaDataMap*) + 391
18 com.adobe.InDesign.SlugCubed 0x23d15df0 SlugMechMetaDataClientNotify::OnMetaDataUpdate(IDAAttributeGroup*, IMechMetaDataMap*, IMechMetaDataMap*, IMechMetaDataMap*) + 512
19 com.adobe.InDesign.MechCubed 0x23b8fbf4 MechMetaDataServiceUtils::MetaDataContentChangeNotify(IDAAttributeGroup*, IMechMetaDataMap*, IMechMetaDataMap*, IMechMetaDataMap*, IDType<ClassID_tag> const&) + 436
20 com.adobe.InDesign.MechCubed 0x23b3ef2d MechUtils::DoMetaDataNotify(IDAAttributeGroup*, short, IMechMetaDataMap*, IMechMetaDataMap*) + 157
21 com.adobe.InDesign.MechCubed 0x23b47cd3 MechUtils::DoPromptAndAnalysis(PromptAnalysisParams const&) + 723
22 com.adobe.InDesign.MechCubed 0x23b2da27 MechDocMetaDataMgr::DoPromptAndAnalysis(long, IDAAttributeGroup*, short) + 103
23 com.adobe.InDesign.MechCubed 0x23b3ee36 MechUtils::DoPromptUpdate(UIDRef const&, long, short, IPMUnknown*, IDType<PMIID_tag> const&, long) + 214
24 com.adobe.InDesign.MechCubed 0x23b12238 MechDocFileHandler::OnSave(UIDRef const&, long, K2::UIFlags, long) + 200
25 com.adobe.InDesign.MechCubed 0x23b128d9 MechDocFileHandler::Save(UIDRef const&, K2::UIFlags) + 185
26 com.adobe.InDesign.MechCubed 0x23b12c9c MechDocFileHandler::Close(UIDRef const&, K2::UIFlags, unsigned char, IDocFileHandler::CloseCmdMode) + 684
27 WidgetBinLib.dylib 0x02b33049 DocumentPresentation::ClosePresentation(IDocumentPresentation::SchedulingBehavior, short) + 569
28 ...obe.InDesign.Application UI 0x1b2f8099 GetPlugIn + 691433
29 com.apple.HIToolbox 0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
30 com.apple.HIToolbox 0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
31 com.apple.HIToolbox 0x94c4a3e0 SendEventToEventTargetWithOptions + 58
32 com.adobe.owl 0x02c91966 OWLThemeAddBrush + 7174
33 com.adobe.owl 0x02d5ae71 OWLDocumentCreateNonComposite + 3627
34 com.adobe.owl 0x02cac140 OWLPaletteCreateNonComposite + 22850
35 com.adobe.owl 0x02cf495b OWLDockGetAnchor + 20221
36 com.adobe.owl 0x02cfbed9 OWLDockGetAnchor + 50299
37 com.adobe.owl 0x02c902f4 OWLThemeAddBrush + 1428
38 com.apple.HIToolbox 0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
39 com.apple.HIToolbox 0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
40 com.apple.HIToolbox 0x94c4a3e0 SendEventToEventTargetWithOptions + 58
41 com.adobe.owl 0x02c91966 OWLThemeAddBrush + 7174
42 com.adobe.owl 0x02cc89d7 OWLPaletteCreateNonComposite + 139737
43 com.adobe.owl 0x02cfd08f OWLDockGetAnchor + 54833
44 com.adobe.owl 0x02c902f4 OWLThemeAddBrush + 1428
45 com.apple.HIToolbox 0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
46 com.apple.HIToolbox 0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
47 com.apple.HIToolbox 0x94c66ecc SendEventToEventTarget + 52
48 com.apple.HIToolbox 0x94d55de0 HIWindowButtonView::SendWindowEvent(unsigned long, unsigned long) + 208
49 com.apple.HIToolbox 0x94d55d06 HIWindowButtonView::ControlHitSelf(OpaqueControlRef*, short, unsigned long) + 156
50 com.apple.HIToolbox 0x94c5b357 HIView::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 9533
51 com.apple.HIToolbox 0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
52 com.apple.HIToolbox 0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
53 com.apple.HIToolbox 0x94c66ecc SendEventToEventTarget + 52
54 com.apple.HIToolbox 0x94cc0a45 SendControlHit(HIView*, OpaqueEventRef*, short, unsigned long) + 297
55 com.apple.HIToolbox 0x94cc08c5 HIView::NotifyControlHit(OpaqueEventRef*, short, unsigned long) + 45
56 com.apple.HIToolbox 0x94d2a7d8 HIView::ClickInternal(CGPoint const&, unsigned long, void (*)(OpaqueControlRef*, short), OpaqueEventRef*, bool) + 254
57 com.apple.HIToolbox 0x94d16fb6 HIView::ClickSelf(OpaqueEventRef*) + 370
58 com.apple.HIToolbox 0x94c59771 HIView::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2391
59 com.apple.HIToolbox 0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
60 com.apple.HIToolbox 0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
61 com.apple.HIToolbox 0x94c66ecc SendEventToEventTarget + 52
62 com.apple.HIToolbox 0x94d145f7 HIView::Click(OpaqueEventRef*) + 329
63 com.apple.HIToolbox 0x94d14459 HandleClickAsHIView(OpaqueWindowPtr*, OpaqueEventRef*) + 151
64 com.apple.HIToolbox 0x94d13de9 HandleWindowClick(OpaqueWindowPtr*, Point, short, unsigned long, OpaqueEventRef*) + 505
65 com.apple.HIToolbox 0x94d13bdb HandleMouseEvent(OpaqueEventHandlerCallRef*, OpaqueEventRef*) + 791
66 com.apple.HIToolbox 0x94ccf602 StandardWindowEventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 96
67 com.apple.HIToolbox 0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
68 com.apple.HIToolbox 0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
69 com.apple.HIToolbox 0x94cbc3d7 CallNextEventHandler + 95
70 com.adobe.owl 0x02cfcc8b OWLDockGetAnchor + 53805
71 com.adobe.owl 0x02c902f4 OWLThemeAddBrush + 1428
72 com.apple.HIToolbox 0x94c4b13d DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
73 com.apple.HIToolbox 0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
74 com.apple.HIToolbox 0x94c66ecc SendEventToEventTarget + 52
75 com.apple.HIToolbox 0x94c79603 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 2579
76 com.apple.HIToolbox 0x94c4b4f6 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2134
77 com.apple.HIToolbox 0x94c4a57b SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
78 com.apple.HIToolbox 0x94c66ecc SendEventToEventTarget + 52
79 ...adobe.InDesign.AppFramework 0x1946b13f 0x19468000 + 12607
80 ...adobe.InDesign.AppFramework 0x194905fa GetPlugIn + 14282
81 com.adobe.InDesign 0x000028ab main + 187
82 com.adobe.InDesign 0x000027c6 start + 54
By the way, I tried simply deactivating the UTS plug-in, and completely uninstalling it, and it still crashes when trying to save the InDesign file after a PDF export (with preflight turned off, as previously discussed).
I have found that I can Save the files first, then PDF them, and close them without saving it, without a problem.
It looks to me in the crash report above that the Extensis Autoactivation plugin is active. Matthew asked me to try the export with the plugin turned off, which you can do in Suitcase > Manage Plugins, then restart InDesign. That resolved the issue for me when working with Matthew, and I'm sure he'd ask you to try the same thing to corroborate. I sent my collected InDesign file to Matthew and his team for testing and they were able to duplicate the problem.
I'm using Universal Type Server, which is the Industry Class Workgroup version of little brother Suitcase, and I don't see any option for Managing Plug-Ins. Anyone else with UTS know where this Manage Plug-Ins option might be in UTS?
As I mentioned, though, I also tried completely removing the plug-in and still got the crash.
Right, but now with Universal Type Server. I should mention that there is an option for turning Auto-Activation on and off under this menu, but not for "managing the plug-in" or deactivating it entirely. And hence, it still shows up in the crash report.
However, completely uninstalling it, as mentioned before, does the trick as far as it not showing up in the crash report (which I will include below). But does not solve the crashing itself.
Here are the options available, when using UTS (screen shot).
I meant "100% CPU or 0% CPU."
No, the amount of RAM isn't really that interesting. The amount of
processor time is. Is InDesign working really hard trying to do
something over and over? Or is it sitting there waiting for another
component to do something?
But most importantly:
"Press the Sample Process" button.
That was really the most critical part. It will tell you what
InDesign is doing. Without that, everyone is just guessing in the
dark. (Which is silly).
Good to see you got an actual crash report though.
Nothing in it really jumps out at me -- it looks like perhaps
the layout is just corrupt. But I'm not an Adobe Developer, so my
analysis is limited.
Confirm again that you trashed your preferences and saved the file
as IDML and re-opened the IDML file?
by the way: It's not a good idea to paste these hundreds of lines onto
the forum -- it makes the threads nearly impossible to read. If you're
not sure what's relevant (usually for crashes it's just the Thread 0
part), please use pastebin.com or a similar service.
Okay, well I will give it a shot again, later, and I'll also try the thing for posting the crash log in a more tidy manner.
Meanwhile, I'm on someone else's dime here, so I've actually got to get some work done today, too. LOL
I did not go so far as going to an IDML file. But I did completely remove Universal Type Server Plug-In components, and rebooted the computer, to make sure that InDesign was not "hanging onto anything".
I would have to totally rule out the assumption of a corrupt layout. Up until this week, it was crashing on every second document opened after an InDesign restart. Today, it was crashing on every document that I tried to save after creating a PDF.
If you have an existing layout that you're working on that crashes,
take the 5 seconds save it as IDML and re-open it. It'll be faster
than the crash recovery would be, and you'll have the strong assurance
that you've removed corruption, at least to the best degree we know
how to do.
It sounds like there's something else going on here, though.
Are your documents starting clean and fresh, or are you using an
As a printing company, we have a pretty fair mix of files: Some fresh, some from Templates, some from Design Firms outside the company.
It is happening with all files.
I'm somewhat worried about what might be lost saving files as IDML. Especially with customer files. I was under the impression that the main point of saving an IDML was to be able to open in a lower version of InDesign.
IDML does not lose information (nor does INX, its predecessor).
It is designed to write files in a format that can be parsed by
third-party software and tools, so it is XML-based and very structured
and the structure is publicly documented.
Around here, most people use it for its other attributes -- that CS4 can
read CS5 IDML files. But when that happens, CS4 throws away the information
it doesn't understand when it opens the file -- CS5 does not throw it away
when it writes the file.
But think of it less as a solution and more of an experiment to help us
understand your problem. If a crash that reliably happens goes away
when you round-trip through IDML, that tells you that you are seeing
Which reminds me -- are you using a network filesystem? Have you tried
keeping the files locally on your hard drive?
John, thanks for that explanation. That makes me feel a lot better about using that process. I had seen the loss when opening up the files in an earlier version. But your explanation helps me to understand that it is not the fault of the format, and that if opened back up in CS5, all should be well and good.
Yes, all files are stored out on a PC file system. I loved it when our files were stored on a Mac raid server. And a lot of times that is the solution to problems, but not in this case. I gave that a go early on.
I am more than willing to give the IDML thing a go, just for the purpose of eliminating one other variable. However, I have a hard time believing that files are just randomly corrupt, on various machines throughout the shop, and with a variety of files from various sources, some of which have never been out on the server.
This problem for us occurred when we upgraded from CS4 to CS5 and the advent of the background PDF. So, I seriously tend to think that the problem is program specific, not file specific.
I agree, nobody has a good idea what the problem is. But it's
definitely the case that you're seeing something that is not normal
for CS5 users. And if you're seeing it on multiple machines, it has to
be something about your environment. I don't know what. So we're kind
of grasping at straws, trying things that aren't extremely likely, so
we have to look at things that are less likely...
OK, so where are we?
Peter (et al), if you want to edit out the long long crashlog from post #255, claidheamdanns has posted it to http://pastebin.com/a0YypR2r (he PM'd me with it) and that'll make the thread a bit readable again.
claidheamdanns, it sounds like you are seeing multiple problems. After all, you started out with an occasional problem, you determined it was triggered by Preflight, then you started seeing it everywhere, and on every other document.
So you may have multiple interrelated issues. So I think you need to try all the solutions we have in our bag of tools (meager as it is!), because one soluton may be insufficient to fix the problem. So that means:
- Test with local files, not files on networked servers
- Test with clean files, not those that might already be corrupt, and especially not those imported from CS3 or CS4
- Test without any font managers installed, Suitcase, UTM, or any such thing.
- Trash your preferences
- Hangs are not crashes. They may have different causes (or they may not).
Both of your crash reports are are very similar, and are pretty deep -- 82 levels deep in the stack, crashing in com.adobe.InDesign.Text, in areas that may have to do with plugins (GetPlugIn+1096990, etc.) and in the normalization of saved data (VOS_SavedData::Normalize()). I'm not familiar with those particuliar functions, but they imply corruption to me.
We also haven't seen the call graph from Sample Process in Activity Monitor, either.
I think that's about the size of it from where I sit...
An excellent question. I don't intend to upgrade to the .5 version, as from what I've seen so far it doesn't offer me enough incentive to do so. But if the bug is not fixed in the current CS5 (as opposed to fixing it in 5.5) I'll be most upset. It's cost me around eight work days in time seeking workarounds, trying to fix it and rebuilding templates in CS4, and I've now reverted to CS4 in frustration.
That reversion was interesting though. The CS5 installation was on a clean, new computer so CS4 was not present. I thought I'd try loading it (Indesign alone), without removing CS5 (having seen reports that they had to be installed in the correct order). It went in fine (demanding to add Bridge CS4, which wasn't wanted) and both it and CS5 work without problems, and no reloading CS5.
I can tell you that we have one known cause of failure that was fixed in 7.0.3. We also have a reproducible case which is under investigation, but did not make it into CS 5.5, so I can't say when that will be addressed. However, the bulk of the failures I've seen, based on crash logs, are due to issues with Extensis's auto-activation plug-ins, and we are actively engaged with them to see if they can modify their plug-ins to account for our background PDF exporting.
If recent history is an indication, you can expect more bug fixes for CS5. There was even an official update for CS4 not to long ago and developers who have access to the rapid release program have gotten CS3 updates as recently as 4 months ago and CS4 updates as recently as 2 months ago...
FWIW, The IS a 7.0.4 update on the horizon which fixes a couple of bugs that affected me personally...
Of course, whether there will be a 7.0.5 update that will make it to the masses still remains to be seen. If there are major bugs fixed, I'd bet on yes.