Data Merge causing rip to choke

I have a newsletter cover (8.5" x 5.5" folded in half) that has an image on the front with an address that goes on the back. I figured if I put the image and other repeating elements on the master page and having just the address data on the document pages that that would make for a less "heavy" file. The result of the Data Merge is a 1,250 page document. I sent half of the document to the printer but it didn't want to print it.
I am now sending it to the printer 100 pages at a time. Any suggestions to be able to print a multipage data merged file without having to send it in such small increments?
TIA,
Jeff
MacPro 4-core, 8GB RAM, Snow, CS5 (7.0.4), Canon 9075 pro copier w/bustled Fiery

When you created the merge, did you create a new Indesign document or did you export to PDF? If you exported to PDF, this method utilizes Forms xObjects, which writes data for a static element just once, as opposed to writing data for the object every page. And this ultimately would creating a much lighter file. To fully reap the benefits of this workflow, your Fiery RIP would have to be compliant for PDF XObjects, and you would have to submit the PDF, as opposed to printing postscript to the device.

Similar Messages

Data Merge Causing Crash in CS2 (Windows XP)

I'm working with 3 quarterly reports that merge data from a CSV file to multiple fields. Each report uses a separate CSV file.
I've reused these reports each time I need to create a new report. Each time I make necessary edits to the report (new pics, copy, etc), link to a new data source (CSV with current data) and resave under a different name.
I'm in the process of creating this quarter's reports, however when I click on the Data Merge palette tab, In Design crashes and it shuts down. This has happened on in the past (on occasion) for one report, but I usually can work around it by taking one of the other two reports and adjusting it accordingly. In some cases I think I was eventually able to use the offending file. However this time the problem is happening for all 3 reports and after repeated tries I'm not getting anywhere to figure out the cause let alone resolve it.
Has this happened to anyone? Any help would be great.

Not sure how to link to this, but go back through the forum and look for the topic posted below. I think this may resolve your issue ... it worked for me and it sounds like a similar issue. When you are following the directions, make sure that you save your Printer and Document Presets (if you have any setup) first.
Good luck!
-Scott
Topic
Data Merge - Memory Could Not be Written - Crashes Every Time now
Scott Piegza - 07:44am Jan 11, 2008 Pacific
I am having some pretty serious issues whenever I try to access a .csv or .txt file from the DataMerge Palette. It seems to load, but when I try to expand the window to see the available fields, it "thinks" for a few seconds, then delivers an InDesign.exe - Application Error indicating:
The instruction at "0x4edb29c1" referenced memory at 0x03380000". The memory could not be "written". Click OK to terminate the program | Click on CANCEL to debug the program.
At this point, no matter the response the program terminates. This is consistent every time I try to open a file from the datamerge palette although the actual referenced memory may change ... not sure, just a bunch of numbers to me. I use datamerge extensively and it was previously working fine, not sure what the action was that led to the change.
Any suggestions would be greatly appreciated!
Thanks!
-Scott

Data merge causing layout shift

I am having an issue merging multiple records on a single Master page resulting in the entire page ending up offset when merged. Using InDesign 5.5.
I have tried starting over with a new file and skipping the preview step, because I have read preview in 5.5 might have glitches, but this doesn't seem to solve the problem. My entire text block with multiple merge fields and all the images scoot over to the right and down a few inches when merged. When I have done a preview, however, everything looks fine until I actually merge. The merge fields do end up in the right place on all the pages.
Any suggestions? I'm merging tp pdf with an Excel csv file. Thanks.

@OP:
so far as uploading the assets to the web for us to test and replicate the fault, perhaps try the dropbox service or similar FTP service.
more importantly
after looking at the screengrab, i think the opening post was confusing. can you please confirm that when the merge is made, is the merge meant to be:
* 1 record output per page (like a direct mail letter); or
* many records output per page (like LincolnPrintingPlus's gift certificate post)
also, what page is the merge being assembled on? an actual MASTER PAGE e.g.
or page 1 of the file with the master BLANK:
if the answer is one record per page and art is made on page 1 and the master is blank, there should be no issues. Having said that, we need to have access to all the assets to replicate the fault.

Data merge crash in ID CS6 server (but works in ID CS6 desktop)

I have a strange problem with datamerge solution of InDesign cs6 server.
There is a 20-page indd document and a 50-record csv file to be used along with it.
Creating merged document (using data merge) causes ID CS6 server to crash right after the moment the following line executes:
objDoc.mergeRecords();
However, strangely, for the same template file there is no crash in InDesign desktop counterpart.
I certainly seems that there is some inherent problem with data merge in the InDesign server. All data merge settings are same for both applications.
Even there is no crash if I directly export to PDF as follows:
objDoc.dataMergeProperties.exportFile(ExportFormat.PDF_TYPE, outputfile);
So, in summary for the same template file:
objDoc.mergeRecords(); // crash occurs in InDesign server but not in desktop counterpart
objDoc.dataMergeProperties.exportFile(...); // no crash at all
It would be a great help if someone can throw some light on this.

This is two separate issues. The highlighting is a behavior change and not for the better inthe opinion of many, but nothing you can do about it at the moment.
Links, on the other hand, have ALWAYS been absolute, as long as ID can find them in the path stored in the file. Even if you copy a links folder from the server to the local machine, ID is going to ignore it and use the links on the server as long as they are there and you have a connection.

Crazy long rip times on Data Merge Documents

Hello Everyone,
I am digital printer and I am running to a strange problem with Data Merge. I am making a post card for a customer that needs addresses added to them. I do these kinds of orders all the time and usually I can just place the post card in Indesign cs6 and use date merge to apply the addresses. Typically this works easily and without any fuss. However I just created a new card in Indesign. Exported it as a pdf and then placed it back in indesign for addressing. Now when I try to print my card it is taking an hour and a half to rip the file on my Fiery Command Work Station. Typically a job like this will rip in no more than a minute or two. Does any one know what might be causing this? I have tried flettening the pdf in photoshop to maybe help simplify the file but no luck. I designed the card in Indesign cs6 on a mac running 10.7.5 and I am using Command Work Station 5.5 on Fiery , printing on a Xerox 700 digital press.

Absolutely not.
(1)     PDF/VT-1 files must also be PDF/X-4 files. The “create PDF via distillation of PostScript” method precludes this since PostScript supports neither live transparency nor color management.
(2)     The efficiencies of PDF/VT-1 require use of Forms XOjects and Image XObjects in the PDF file. That requires direct PDF creation that you get from PDF export. This is not available via any route that uses stink'in PostScript as an intermediary.
(3)     Adobe most strongly endorses PDF creation from InDesign via the export function, not printing to PostScript and distilling. Such PostScript is optimized strictly for printing and not for PDF file creation.
          - Dov

Data merge with football tickets. Printing causes out of memory errors. Can only print 10 at a time!

Here's the deal. Printing football tickets for the local high school. 10 tickets per 8.5 x 11 sheet. All black and white. I couldn't data merge into one whole document of tickets because it was failing to do that. So, I end up with 3 documents. First two have 50 pages of tickets and the last has 37 pages.
When I go to print, I can only print 10 pages at a time or InDesign straight up crashes or I get an "Out of Memory" error which is bull because I've got plenty of ram available (unless it's complaining about lack of HD space for some reason)
Incredibly frustrating.
Each ticket has 3 images on it. Two of the images are the same. Those two images are about 103kb .ai files. Very very simple. The other image is a TIFF that is about 76kb. So there are 1000 .ai files / document and 500 TIFFs.
Here's a video I took of it ripping: http://www.youtube.com/watch?v=UCjvdmXuaYs&feature=c4-overview&list=UUf_1UFp80YLZJfCyIxXEg kg
Also, when printing, I have the Send Data set to Optimized Subsampling instead of "All". That's not seeming to help.
Any thoughts?
IDCS 5.5
OSX 10.8.4

I just ran a sample on my laptop.
AI file, duplicated, is 284k. Image is roughly 200k. The CSV has 2054 records, and the merged document with 10 per page is 250 megabytes. PDF is just under 50 megs.
This laptop has only 4 gigs memory but has a lot of free disk space. It took a good amount of time to do the merge, a bit longer to create the PDF-X1a PDF.
Mike

Empty fields in data merge is causing blank lines to show up. CS4

I had this problem when I was laying out my data merge info I origionally put phone and cell phone on the same line which resaulted in the cell phone number getting split in two since the column wasn't wide enough to show both of them side by side. I then moved the cell phone number down to the next line but the problem I had then was that it would leave a blank line everytime I would come across somebody who didn't have a cell phone number. Does anyone know how I can collapse that empty line when the cell phone line is empty?

See your other thread where you asked about this.

How Do I get data merge to work without creating duplicate pages in a single page native file?

I've called Adobe about this and they indicated it was some kind of setting that needed to be changed in InDesign, but wouldn't tell me how to do it unless I paid for an "incident pack" and talked with technical support.
Problem: I have a single page document in InDesign CS5. It's a direct-mail postcard with large high-res images and complicated graphics on it. I want to merge a list of recipients names/addresses from Excel with this single-page design. Excel document has 2,000 names in it.
I successfully create the merge using InDesign's data merge feature, but it creates a new InDesign document with 2,000 pages in it. Each page is a duplicate of my original file, but with different addresses on each page. Because of the multiple records and the high res images it has created 2,000 duplicates of - InDesign crashes. It also took about 4 hours to do the merge.
There has got to be a better way to merge data w/o it created the same page over and over again.
I can't make a pdf to solve this problem becasue I have to work with an in-house printer and they do a poor job of printing from pdf. So, I always send them native files. This printer does not have variable data software. However, if that is the fast and easy solution to this problem - I will force them to purchase it.
Any advise or solution to this problem would be appreciated. Is there a setting in InDesign that needs to change so it doesn't repeat the single page design 2,000 times and cause InDesign to crash?
Thank you.

That's exactly how Data Merge works. If it's on the page, it gets duplicated. 2000 records is a lot, so I'm not sure if the images or the sheer number is what's slowing things down.
One thing you can try is to moove everything EXCEPT the merge placeholders to a master page, then assign the [None] master to the page with the placeholder anbd do the merge. Change the master to the one with your static content after the merge. That might speed up the merge, but it won't do anything for the file being 2000 pages that each has to RIP for printing. The best way to deal with this is to find a printer who can do VDP printing and give him the template file and your data file, and let him do the merge in the print stream.

[CS5.5/6] - XML / Data Merge questions & Best practice.

Fellow Countrymen (and women),
I work as a graphic designer for a large outlet chain retailer which is constantly growing our base of centers. This growth has brought a workload that used to be manageable with but two people to a never ending sprint with five. Much of what we do is print, which is not my forte, but is also generally a disorganized, ad-hoc affair into which I am wading to try to help reduce overall strain.
Upon picking up InDesign I noted the power of the simple Data Merge function and have added it to our repetoire in mass merging data sources. There are some critical failures I see in this as a tool going forward for our purposes, however:
1) Data Merge cannot handle information stored and categorized in a singular column well. As an example we have centers in many cities, and each center has its own list of specific stores. Data merge cannot handle a single column, or even multiple column list of these stores very easily and has forced us into some manual operations to concatenate the data into one cell and then, using delimiter characters, find and replace hard returns to seperate them.
2) Data Merge offers no method of alternate alignment of data, or selection by ranges. That is to say: I cannot tell Data merge to start at Cell1 in one column, and in another column select say... Cell 42 as the starting point.
3) Data merge only accepts data organized in a very specific, and generally inflexible pattern.
These are just a few limitations.
ON TO MY ACTUAL DILEMMA aka Convert to XML or not?
Recently my coworker has suggested we move toward using XML as a repository / delivery system that helps us quickly get data from our SQL database into a usable form in InDesign.
I've watched some tutorials on Lynda.com and havent yet seen a clear answer to a very simple question:
"Can XML help to 'merge' large, dynamic, data sets like a list of 200 stores per center over 40 centers based off of a single template file?"
What I've seen is that I would need to manually duplicate pages, linking the correct XML entry as I go rather than the program generating a set of merged pages like that from Data Merge with very little effort on my part. Perhaps setting up a master page would allow for easy drag and drop fields for my XML data?
I'm not an idiot, I'm simply green with this -- and it's kind of scary because I genuinely want us to proceed forward with the most flexible, reliable, trainable and sustainable solution. A tall order, I know. Correct me if I'm wrong, but XML is that beast, no?
Formatting the XML
Currently I'm afraid our XML feed for our centers isnt formatted correctly with the current format looking as such:
<BRANDS>
     <BRAND>
          • BrandID = xxxx
          [Brand Name]
          [Description]
          [WebMoniker]
          <CATEGORIES>
               <CATEGORY>
                    • xmlns = URL
                    • WebMoniker = category_type
          <STORES>
               <STORE>
                    • StoreID = ID#
                    • CenterID = ID#
I dont think this is currently usable because if I wanted to create a list of stores from a particular center, that information is stored as an attribute of the <Store> tag, buried deep within the data, making it impossible to 'drag-n-drop'.
Not to mention much of the important data is held in attributes rather than text fields which are children of the tag.
Im thinking of proposing the following organizational layout:
<CENTERS>
     <CENTER>
     [Center_name]
     [Center_location]
          <CATEGORIES>
               <CATEGORY>
                    [Category_Type]
                    <BRANDS>
                         <BRAND>
                              [Brand_name]
My thought is that if I have the <CENTER> tag then I can simply drag that into a frame and it will auto populate all of the brands by Category (as organized in the XML) for that center into the frame.
Why is this important?
This is used on multiple documents in different layout styles, and since our store list is ever changes as leases end or begin, over 40 centers this becomes a big hairy monster. We want this to be as automated as possible, but I'd settle for a significant amount of dragging and dropping as long as it is simple and straightforward. I have a high tollerance for druding through code and creating work arounds but my co-workers do not. This needs to be a system that is repeatable and understandable and needs to be able to function whether I'm here or not -- Mainly because I would like to step away from the responsibility of setting it up every time
I'd love to hear your raw, unadulterated thoughts on the subject of Data merge and XML usage to accomplish these sorts of tasks. What are your best practices and how would you / do you accomplish these operations?
Regards-
Robert

From what I've gleaned through watching Lynda tutorials on the subject is that what I'm hoping to do is indeed possible.
Peter, I dont disagree with you that there is a steep learning curve for me as the instigator / designer of this method for our team, but in terms of my teammates and end-users that will be softened considerably. Even so I'm used to steep learning curves and the associated frustrations -- but I cope well with new learning and am self taught in many tools and programs.
Flow based XML structures:
It seems as though as long as the initial page is set up correctly using imported XML, individual data records that cascade in a logical fashion can be flowed automatically into new pages. Basically what you do is to create an XML based layout with the dynamic portion you wish to flow in a single frame, apply paragraph styles to the different tags appropriately and then after deleting unused records, reimport the XML with some specific boxes checked (depending on how you wish to proceed).
From there simply dragging the data root into the frame will cause overset text as it imports all the XML information into the frame. Assuming that everything is cascaded correctly using auto-flow will cause new pages to be automatically generated with the tags correctly placed in a similar fashion to datamerge -- but far more powerful and flexible.
The issue then again comes down to data organization in the XML file. In order to use this method the data must be organized in the same order in which it will be displayed. For example if I had a Lastname field, and a Firstname field in that order, I could not call the Firstname first without faulting the document using the flow method. I could, however, still drag and drop content from each tag into the frame and it would populate correctly regardless of the order of appearance in the XML.
Honestly either method would be fantastic for our current set of projects, however the flow method may be particularly useful in jobs that would require more than 40 spreads or simple layouts with huge amounts of data to be merged.

Can you place text from a word document using data merge?

I'm working with a charity that is giving away scholarships/grants. I need to create a ducument that pulls in various application data plus their submitted essay (docx format). I would like to do this via data merge but cannot find any reference if it is possible.
Please help, I really need to automate as much as possible since this is a side project.
Kevin

Data merge only collects info from CSV format - which I expect you would export from Excel. (I think it'll take tab-delimited as well, but that's it.)
MS Word files can be placed, but Data Merge is not the tool to automate placing of Word-file content. If there is no formatting of their essays, I suspect you could use VBA to cause entire essays to occupy a single cell in Excel. But that would be the only way to use Data Merge to automate import of essays into InDesign.
Maybe if you tell us more we can give you some more automation suggestions. (I spend a lot of time automating translation workflows, but I still place Word files. All day long, in fact.)
(edited for spelling)

Data Merge Crashing with InDesign CC 9.2

Since I've updated to InDesign CC 9.2, ID crashes when attempting data merges. It's happened on both my Mac computer at work and my personal Mac laptop. I changed out my lists to make sure it wasn't something with my csv file and it still crashed.
I also opened a file that I had successfully merged before doing the update. It crashed when I attempted to create that merged document as well.
As a workaround to get my project done, I was able to make an IDML file from my CC file and open it in CS6 and successfully create my merged document from that.
Anybody else having this issue or know of any fixes or is it a wait for the next version and bug fixes thing?
Thanks in advance.

Exact same issue here. InDesign CC crashes right after the merge every single time.
Backsaved file and opened in InDesign 6 – merged like a charm.
Adobe, please fix the bug in CC.
Thanks!
Process:
Adobe InDesign CC [956]
Path:
/Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/Adobe InDesign CC
Identifier:
com.adobe.InDesign
Version:
9.2.0.69 (9200)
Code Type:
X86-64 (Native)
Parent Process: launchd [131]
User ID:
502
Date/Time:
2014-01-29 11:39:53.838 -0600
OS Version:
Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report:
91088 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 214878 sec
Per-App Crashes Since Last Report:   4
Anonymous UUID:
0B8A413F-AA3A-D340-5BE6-B511CB5CE317
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
*** CFRetain() called with NULL ***
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreFoundation
0x00007fff8e8c1acd CFRetain + 29
1   com.apple.CoreFoundation
0x00007fff8e8cdd57 __CFDictionaryStandardRetainValue + 71
2   com.apple.CoreFoundation
0x00007fff8e8cdb8a __CFBasicHashAddValue + 1226
3   com.apple.CoreFoundation
0x00007fff8e8d4268 CFBasicHashAddValue + 3176
4   com.apple.CoreFoundation
0x00007fff8e8d358d CFDictionaryAddValue + 189
5   com.adobe.InDesign.Document Framework
0x00000001107bb553 0x110697000 + 1197395
6   com.adobe.InDesign.Document Framework
0x00000001107bb117 0x110697000 + 1196311
7   com.adobe.InDesign.AppFramework
0x000000010ba87415 0x10ba60000 + 160789
8   com.adobe.InDesign.AppFramework
0x000000010ba868e3 0x10ba60000 + 157923
9   PublicLib.dylib
0x00000001011ae781 CSubject::Change(IDType<ClassID_tag>, IDType<PMIID_tag> const&, void*) + 81
10 com.adobe.InDesign.Document Framework
0x00000001107dab2f 0x110697000 + 1325871
11 com.adobe.InDesign.Document Framework
0x00000001107d8fd4 0x110697000 + 1318868
12 PublicLib.dylib
0x00000001010efd01 Command::DoImmediate(short) + 33
13 com.adobe.InDesign.Utilities
0x00000001087a541c 0x1087a3000 + 9244
14 com.adobe.InDesign.Utilities
0x00000001087a55a5 0x1087a3000 + 9637
15 com.adobe.InDesign.AppFramework
0x000000010ba6bb1f 0x10ba60000 + 47903
16 PublicLib.dylib
0x00000001010eefc0 CmdUtils::ProcessCommand(ICommand*) + 64
17 com.adobe.InDesign.Document Framework
0x00000001107d9c77 0x110697000 + 1322103
18 com.adobe.InDesign.DataMerge
0x000000011808c51d 0x11804d000 + 259357
19 com.adobe.InDesign.DataMerge
0x000000011808c3a1 0x11804d000 + 258977
20 com.adobe.InDesign.DataMerge
0x000000011808b1ab 0x11804d000 + 254379
21 com.adobe.InDesign.DataMergeUI
0x0000000118112fbb 0x11810e000 + 20411
22 com.adobe.InDesign.DataMergeUI
0x00000001181114e4 0x11810e000 + 13540
23 com.adobe.InDesign.Actions
0x0000000116d80189 0x116d69000 + 94601
24 com.adobe.InDesign.DataMergeUI
0x000000011812d866 0x11810e000 + 129126
25 com.adobe.InDesign.AppFramework
0x000000010ba87415 0x10ba60000 + 160789
26 com.adobe.InDesign.AppFramework
0x000000010ba868e3 0x10ba60000 + 157923
27 PublicLib.dylib
0x00000001011ae781 CSubject::Change(IDType<ClassID_tag>, IDType<PMIID_tag> const&, void*) + 81
28 com.adobe.InDesign.DV_Widgets
0x00000001166b1e8c 0x1166ab000 + 28300
29 com.adobe.InDesign.DV_Widgets
0x00000001166b29a3 0x1166ab000 + 31139
30 com.adobe.InDesign.DV_Widgets
0x00000001166b2a61 0x1166ab000 + 31329
31 DV_WidgetBinLib.dylib
0x000000010005c0cc DVIconSuiteButtonView::ChangeControls(short) + 92
32 DV_WidgetBinLib.dylib
0x000000010005d709 0x100037000 + 157449
33 com.adobe.dvaui.framework
0x00000001009dcebf dvaui::controls::UI_ControlView::SendControlMessages(dvacore::utility::SharedFunctions<bo ost::shared_ptr<boost::function<void (dvaui::ui::MessageT<dvaui::ui::UI_Node>*)> > > const&, dvaui::ui::MessageT<dvaui::ui::UI_Node>*) + 63
34 com.adobe.dvaui.framework
0x00000001009b986c dvaui::controls::UI_Button::SendButtonChangedMessage(dvacore::utility::Flags<unsigned char>) + 76
35 com.adobe.dvaui.framework
0x00000001009b89dc dvaui::controls::UI_Button::PerformAction(bool, dvacore::utility::Flags<unsigned char>, bool) + 108
36 com.adobe.dvaui.framework
0x00000001009b9412 dvaui::controls::ButtonInputCapture::End() + 146
37 com.adobe.dvaui.framework
0x0000000100bbc7c7 dvaui::ui::EventCapture::InvokeEnd(bool) + 135
38 com.adobe.dvaui.framework
0x0000000100bc5e75 dvaui::ui::UI_NodeManager::EndInputCapture(bool) + 101
39 com.adobe.dvaui.framework
0x00000001009b9609 dvaui::controls::ButtonInputCapture::DoMouseEvent(dvaui::ui::MouseEvent const&) + 281
40 com.adobe.dvaui.framework
0x0000000100bd018a dvaui::ui::UI_Node::UI_DispatchCapturedMouseEvent(dvaui::ui::MouseEvent const&) + 650
41 com.adobe.dvaui.framework
0x0000000100bcf5da dvaui::ui::UI_Node::UI_DispatchMouseEventToTarget(dvaui::ui::UI_Node*, dvaui::ui::MouseEvent const&, bool) + 1098
42 com.adobe.dvaui.framework
0x0000000100bcf155 dvaui::ui::UI_Node::UI_DispatchMouseEvent(dvaui::ui::MouseEvent const&, bool) + 69
43 com.adobe.dvaui.framework
0x0000000100c4919a dvaui::ui::OS_View::UI_DispatchPlatformMouseEvent(dvaui::ui::MouseEvent const&, bool) + 666
44 com.adobe.dvaui.framework
0x0000000100c48cfd dvaui::ui::OS_View::UI_DispatchPlatformMouseClickEvent(dvaui::ui::OS_Event const&) + 477
45 com.adobe.dvaui.framework
0x0000000100c475e8 dvaui::ui::OS_View::UI_DispatchEvent(dvaui::ui::OS_Event*) + 120
46 com.adobe.dvaui.framework
0x0000000100c47546 dvaui::ui::OS_View::UI_HandleOSEvent(dvaui::ui::OS_Event*) + 22
47 com.adobe.dvaui.framework
0x0000000100c487f9 dvaui::ui::OS_View::UI_HandlePlatformEvent(NSEvent*) + 57
48 com.adobe.dvacore.framework
0x0000000100679164 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 68
49 com.adobe.InDesign.Application UI
0x000000010faf83a2 0x10f9ca000 + 1237922
50 com.adobe.dvacore.framework
0x00000001006791fc void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 140
51 com.adobe.dvacore.framework
0x000000010067ad6d void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 125
52 com.adobe.dvaui.framework
0x0000000100c538ba dvaui::ui::OS_NodeTimerData::RemoveTimer() + 28442
53 com.apple.AppKit
0x00007fff9051a5d6 -[NSWindow sendEvent:] + 7053
54 com.adobe.owl
0x0000000100481690 0x10044a000 + 226960
55 com.apple.AppKit
0x00007fff90516644 -[NSApplication sendEvent:] + 5761
56 com.adobe.dvaui.framework
0x0000000100c4cd8e dvaui::ui::OS_NodeTimerData::RemoveTimer() + 1006
57 com.adobe.exo.framework
0x00000001028d2420 exo::app::OS_AppBase::SetResetMenuShortcutsOnClose(bool) + 800
58 DV_WidgetBinLib.dylib
0x00000001000c1095 0x100037000 + 565397
59 com.adobe.InDesign.Application UI
0x000000010fafdbcc 0x10f9ca000 + 1260492
60 com.apple.AppKit
0x00007fff9042c21a -[NSApplication run] + 636
61 com.adobe.exo.framework
0x00000001028d1e58 exo::app::OS_AppBase::RunEventLoop() + 56
62 com.adobe.InDesign.AppFramework
0x000000010bb6f8d3 0x10ba60000 + 1112275
63 com.adobe.InDesign.AppFramework
0x000000010bb6e9b2 0x10ba60000 + 1108402
64 com.adobe.InDesign
0x0000000100001dbc main + 412
65 com.adobe.InDesign
0x0000000100001bb4 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib
0x00007fff983cdd16 kevent + 10
1   libdispatch.dylib
0x00007fff983dbdea _dispatch_mgr_invoke + 883
2   libdispatch.dylib
0x00007fff983db9ee _dispatch_mgr_thread + 54
Thread 2:
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccaff3 _pthread_cond_wait + 927
2   com.apple.CoreServices.CarbonCore
0x00007fff95390406 TSWaitOnConditionTimedRelative + 163
3   com.apple.CoreServices.CarbonCore
0x00007fff952f2a98 MPWaitOnQueue + 252
4   PMRuntime.dylib
0x0000000101682be1 0x101681000 + 7137
5   com.apple.CoreServices.CarbonCore
0x00007fff953677e0 PrivateMPEntryPoint + 58
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 3:: com.apple.CFSocket.private
0   libsystem_kernel.dylib
0x00007fff983cd322 __select + 10
1   com.apple.CoreFoundation
0x00007fff8e933f46 __CFSocketManager + 1302
2   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
3   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 4:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3   com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4   com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 5:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3   com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4   com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 6:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3   com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4   com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 7:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3   com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4   com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 8:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3   com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4   com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 9:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3   com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4   com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 10:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3   com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4   com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 11:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3   com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4   com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 12:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib
0x00007fff983cb686 mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff983cac42 mach_msg + 70
2   com.apple.CoreFoundation
0x00007fff8e8ef233 __CFRunLoopServiceMachPort + 195
3   com.apple.CoreFoundation
0x00007fff8e8f4916 __CFRunLoopRun + 1078
4   com.apple.CoreFoundation
0x00007fff8e8f40e2 CFRunLoopRunSpecific + 290
5   com.apple.Foundation
0x00007fff93962546 +[NSURLConnection(Loader) _resourceLoadLoop:] + 356
6   com.apple.Foundation
0x00007fff939c0562 __NSThread__main__ + 1345
7   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
8   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 13:
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.AppFramework
0x000000010bb59a82 0x10ba60000 + 1022594
3   com.adobe.InDesign.AppFramework
0x000000010bb59077 0x10ba60000 + 1020023
4   com.adobe.InDesign.AppFramework
0x000000010bb565f7 0x10ba60000 + 1009143
5   com.adobe.InDesign.AppFramework
0x000000010bb5a61d 0x10ba60000 + 1025565
6   com.adobe.InDesign.AppFramework
0x000000010bb5a5a3 0x10ba60000 + 1025443
7   com.adobe.InDesign.AppFramework
0x000000010bb5a562 0x10ba60000 + 1025378
8   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
9   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
10 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 14:
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.AppFramework
0x000000010bb59a82 0x10ba60000 + 1022594
3   com.adobe.InDesign.AppFramework
0x000000010bb59077 0x10ba60000 + 1020023
4   com.adobe.InDesign.AppFramework
0x000000010bb565f7 0x10ba60000 + 1009143
5   com.adobe.InDesign.AppFramework
0x000000010bb5a61d 0x10ba60000 + 1025565
6   com.adobe.InDesign.AppFramework
0x000000010bb5a5a3 0x10ba60000 + 1025443
7   com.adobe.InDesign.AppFramework
0x000000010bb5a562 0x10ba60000 + 1025378
8   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
9   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
10 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 15:
0   libsystem_kernel.dylib
0x00007fff983cd386 __semwait_signal + 10
1   libsystem_c.dylib
0x00007fff8dd507c8 nanosleep + 163
2   com.adobe.InDesign.Support for JavaScript
0x0000000113a517e8 0x1139fe000 + 341992
3   com.adobe.InDesign.Support for JavaScript
0x0000000113a38a0e 0x1139fe000 + 240142
4   com.adobe.InDesign.Support for JavaScript
0x0000000113a513a5 0x1139fe000 + 340901
5   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 16:
0   libsystem_kernel.dylib
0x00007fff983cd2aa __recvfrom + 10
1   ServiceManager-Launcher.dylib
0x000000011090d1a1 0x1108f5000 + 98721
2   ServiceManager-Launcher.dylib
0x000000011090c4bc 0x1108f5000 + 95420
3   ServiceManager-Launcher.dylib
0x000000011090b55e 0x1108f5000 + 91486
4   ServiceManager-Launcher.dylib
0x000000011090b5cc 0x1108f5000 + 91596
5   ServiceManager-Launcher.dylib
0x00000001109061c4 0x1108f5000 + 70084
6   ServiceManager-Launcher.dylib
0x0000000110906bde 0x1108f5000 + 72670
7   ServiceManager-Launcher.dylib
0x0000000110906aeb 0x1108f5000 + 72427
8   ServiceManager-Launcher.dylib
0x000000011090a24e 0x1108f5000 + 86606
9   ServiceManager-Launcher.dylib
0x000000011090a392 0x1108f5000 + 86930
10 ServiceManager-Launcher.dylib
0x000000011090a14d 0x1108f5000 + 86349
11 ServiceManager-Launcher.dylib
0x000000011090a0c6 0x1108f5000 + 86214
12 ServiceManager-Launcher.dylib
0x00000001108f87d6 0x1108f5000 + 14294
13 ServiceManager-Launcher.dylib
0x00000001108fc9c5 0x1108f5000 + 31173
14 ServiceManager-Launcher.dylib
0x000000011090ad2c 0x1108f5000 + 89388
15 ServiceManager-Launcher.dylib
0x000000011090ce63 0x1108f5000 + 97891
16 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
17 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 17:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3   com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4   com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 18:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3   com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4   com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 19:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3   com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4   com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 20:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3   com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4   com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 21:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3   com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4   com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 22:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3   com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4   com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 23:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3   com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4   com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 24:: UxTech Queue ThreadController
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3   com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4   com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 25:
0   libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1   com.adobe.PDFL
0x000000012a254356 0x129e45000 + 4256598
2   com.adobe.PDFL
0x000000012a254df2 0x129e45000 + 4259314
3   com.adobe.PDFL
0x000000012a255364 0x129e45000 + 4260708
4   com.adobe.PDFL
0x000000012a254b06 0x129e45000 + 4258566
5   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 26:
0   libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1   com.adobe.PDFL
0x000000012a254356 0x129e45000 + 4256598
2   com.adobe.PDFL
0x000000012a254df2 0x129e45000 + 4259314
3   com.adobe.PDFL
0x000000012a255364 0x129e45000 + 4260708
4   com.adobe.PDFL
0x000000012a254b06 0x129e45000 + 4258566
5   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 27:
0   libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1   com.adobe.PDFL
0x000000012a254356 0x129e45000 + 4256598
2   com.adobe.PDFL
0x000000012a254df2 0x129e45000 + 4259314
3   com.adobe.PDFL
0x000000012a255364 0x129e45000 + 4260708
4   com.adobe.PDFL
0x000000012a254b06 0x129e45000 + 4258566
5   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 28:
0   libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1   com.adobe.PDFL
0x000000012a254356 0x129e45000 + 4256598
2   com.adobe.PDFL
0x000000012a254df2 0x129e45000 + 4259314
3   com.adobe.PDFL
0x000000012a255364 0x129e45000 + 4260708
4   com.adobe.PDFL
0x000000012a254b06 0x129e45000 + 4258566
5   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 29:
0   libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1   com.adobe.ACE
0x0000000101b263c7 ACEHasFeature + 533191
2   com.adobe.ACE
0x0000000101b25dc1 ACEHasFeature + 531649
3   com.adobe.ACE
0x0000000101b2567e ACEHasFeature + 529790
4   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
5   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 30:
0   libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1   com.adobe.ACE
0x0000000101b263c7 ACEHasFeature + 533191
2   com.adobe.ACE
0x0000000101b25dc1 ACEHasFeature + 531649
3   com.adobe.ACE
0x0000000101b2567e ACEHasFeature + 529790
4   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
5   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 31:
0   libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1   com.adobe.ACE
0x0000000101b263c7 ACEHasFeature + 533191
2   com.adobe.ACE
0x0000000101b25dc1 ACEHasFeature + 531649
3   com.adobe.ACE
0x0000000101b2567e ACEHasFeature + 529790
4   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
5   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 32:: MPSupport Worker
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   MultiProcessor Support
0x00000001327aafbb 0x132765000 + 286651
3   MultiProcessor Support
0x00000001327aae73 0x132765000 + 286323
4   MultiProcessor Support
0x00000001327caf04 0x132765000 + 417540
5   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 33:: MPSupport Worker
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   MultiProcessor Support
0x00000001327aafbb 0x132765000 + 286651
3   MultiProcessor Support
0x00000001327aae73 0x132765000 + 286323
4   MultiProcessor Support
0x00000001327caf04 0x132765000 + 417540
5   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 34:: MPSupport Worker
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   MultiProcessor Support
0x00000001327aafbb 0x132765000 + 286651
3   MultiProcessor Support
0x00000001327aae73 0x132765000 + 286323
4   MultiProcessor Support
0x00000001327caf04 0x132765000 + 417540
5   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6   libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 35:
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.AppFramework
0x000000010bb59a82 0x10ba60000 + 1022594
3   com.adobe.InDesign.AppFramework
0x000000010bb59128 0x10ba60000 + 1020200
4   com.adobe.InDesign.AppFramework
0x000000010bb565f7 0x10ba60000 + 1009143
5   com.adobe.InDesign.AppFramework
0x000000010bb5a61d 0x10ba60000 + 1025565
6   com.adobe.InDesign.AppFramework
0x000000010bb5a5a3 0x10ba60000 + 1025443
7   com.adobe.InDesign.AppFramework
0x000000010bb5a562 0x10ba60000 + 1025378
8   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
9   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
10 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 36:
0   libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1   libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2   com.adobe.InDesign.AppFramework
0x000000010bb59a82 0x10ba60000 + 1022594
3   com.adobe.InDesign.AppFramework
0x000000010bb59077 0x10ba60000 + 1020023
4   com.adobe.InDesign.AppFramework
0x000000010bb565f7 0x10ba60000 + 1009143
5   com.adobe.InDesign.AppFramework
0x000000010bb5a61d 0x10ba60000 + 1025565
6   com.adobe.InDesign.AppFramework
0x000000010bb5a5a3 0x10ba60000 + 1025443
7   com.adobe.InDesign.AppFramework
0x000000010bb5a562 0x10ba60000 + 1025378
8   com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
9   libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
10 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 37:
0   libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1   libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2   libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3   libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 38:
0   libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1   libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2   libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3   libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 39:
0   libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1   libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2   libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3   libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 40:
0   libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1   libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2   libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3   libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 41:
0   libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1   libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2   libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3   libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x00007fff8ea4d918 rbx: 0x0000000000000000 rcx: 0x00007fff8ea43920 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x00007fff5fbfce60 rsp: 0x00007fff5fbfce50
   r8: 0x0000000000000000   r9: 0x0000000110834d72 r10: 0x0000000110834d72 r11: 0x0000000110834d71
r12: 0x0000000131cd0000 r13: 0x0000000000000000 r14: 0x0000000131cd0000 r15: 0x0000000000000000
rip: 0x00007fff8e8c1acd rfl: 0x0000000000000246 cr2: 0x0000000127355000
Logical CPU: 1
Binary Images:
0x100000000 -
0x100005fff +com.adobe.InDesign (9.2.0.69 - 9200) <B7C09BD6-74AF-323E-8D22-D5E1F7965643> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/Adobe InDesign CC
0x10000c000 -
0x10000eff7 +com.adobe.InDesign.InDesignModelAndUI (9.0 - 0) <612870BE-869E-3165-9714-55F900A66BCC> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/InDesignModelAndUI.framework/Versions/A/InDesignModelAndUI
0x100014000 -
0x10001cfff +com.adobe.coretech.adobesplashkit (AdobeSplashKit Version 1.0 - 1.0) <65BFDA83-4121-3D12-9BBE-9F4FF1DB3D6A> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/Frameworks/AdobeSplashKit.framework/Versions/A/AdobeSplashKit
0x100025000 -
0x10002ffff +ASLSupportLib.dylib (1) <1039F962-C495-36E4-B868-3DA5C43E3EBF> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/ASLSupportLib.dylib
0x100037000 -
0x10013aff7 +DV_WidgetBinLib.dylib (1) <57491245-3B90-3D4B-B4B6-4441EE325E3C> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/DV_WidgetBinLib.dylib
0x1001d5000 -
0x10021aff7 +TextPanelLib.dylib (1) <4B30610F-C637-3910-A413-C40325795CAD> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/TextPanelLib.dylib
0x100237000 -
0x100398fff +WidgetBinLib.dylib (1) <50EE77D3-591B-306F-9D62-2026938837EE> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/WidgetBinLib.dylib
0x10044a000 -
0x100616fff +com.adobe.owl (AdobeOwl version 5.0.24 - 5.0.24) <1C99AA07-E73F-370B-82FA-01C1C4AAF97D> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/Frameworks/AdobeOwl.framework/Versions/A/AdobeOwl
0x100659000 -
0x10089dfff +com.adobe.dvacore.framework (7.0.849324 - 7.0.849324.0) <08EB97C1-03E5-3C1B-B154-C886807BC6F1> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/Frameworks/dvacore.framework/Versions/A/dvacore
0x100964000 -
0x100df1ff7 +com.ad

Multiple Data Merge - Problem Resolve... Sort Of

I've researched this issue all morning and found issues dating back to 2012 regarding the problems with Indesign's Multiple Record Data Merge. Many of the issues are answered with the basic set up. Create a new page as a single page and non facing page document. It appears that an earlier bug was resolved that caused data merge documents to be placed off center when produced. The issue that I was experiencing was similar to what I had seen but not covered or not answered when it appeared someone was posting a question about it.
I started with a single page document, non-facing page, no initial text box, and sized to 8.5'' x 11''. I'm layout out name badges 10-up on a page. I had a previous template that had some graphics in the background for alignment purposes. I created a blank master page and a record holder for the name badge then loaded my data source, placed my data entries, and styled accordingly. Upon creating a data merge I selected Multiple Record and then previewed the data merge and positioned the elements on the page using the data merge controls top, left and column placement commands.
The preview looked perfect. The problem came when I finished the final data merge. The resulting page was not correct and looked nothing like the preview. Records were strewn about the page and excessive amounts of pages were created. I spent 4 hours trouble shooting this, far more than this project was billed. At this point it was a mission. In a reply dated back around 2013 I found that someone had removed a layer from their document. I had no layers. The only thing that was not a part of the actual data merge was the graphics that I had on the page for positioning that were not tied to the data merge at all.
I decided to delete these graphics and try to apply the data merge again. The results were perfect. I'm deducing from this experiment that the data merge needs to be done on a blank page. Which is counter productive to the Indesign mater page template. Any elements on the page need to exist as a a part of your data entry group and no other elements on the page. You only create one data entry group in the top corner of the page then use the data merge panel to position and duplicate. Otherwise, you will get a single page for each record you have with each record set 10-up in my case.
Recap:
Create a single non-facing page document with no intial text box. (if you have more than one page the Multiple Records option will be grayed out)
Only have 1 layer in this document
Set a single data entry set/group on the master page.
Do not include any other graphics. Put them in after the data merge.
Click the Create Merged Document button in the data merge panel
Select "Multiple Records" from the drop down list
Click the Multiple Record Layout tab at the top of the Data Merge panel
Click "Preview Multiple Record Layout" at the bottom of the Data Merge panel so you can see the Entry Sets with the data in place
Use the Margins and Layout or Records inputs to position the elements on the document (see note below)
Click OK when everything is in place the way you like it.
After the data merge is complete you will have a new document that should look like you want it to. Now you can go into this document and start adding your design elements.
NOTE: Positioning the content without the base graphics can be tough if not impossible. What I did in this situation is placed my positioning guides on the page then went through Steps 1-9 to set up the document for merge. Once my settings were set I then clicked "Cancel" and deleted my positioning guides and graphics. The problem I was having was due to these elements being on the page. Once I created the document I then pasted my template guides back into the final data merged master page for production.
Request to ADOBE: Fix this issue so we can design our layouts and position our data merge elements without having to backtrack.

If you insist in multi-record data merge, you can have static/variable graphic and text components work. But, create a 3.5 x 2 frame (3.75 x 2.25 card w/bleed) around all of these components, and make sure nothing extends beyond this bounding frame. If the composition prevents you from enclosing all components, then make a PDF of content that is imported in as one graphic.
Another suggestion: don't combine the functions of variable data merge with imposition.
Create a 1up layout of business card to data merge the variable info.
From this file, export to PDF.
Then impose the individual cards with: an imposition app, PDF plug-in, Indesign script, or even manual placement into another document.

Data Merge Image Size

If I create an image frame and place a data merge field in it, when I do the merge, it makes the image the size of the frame (i.e. either enlarged or shrunk to fit). I would like the image to come in at 100% so that I can use the "fit frame to image" command instead of having to first resize the image back to 100%. I've tried messing with the frame fitting options, but nothing seems to be of any use. If I'm missing something, I hope someone can fill me in.
In the event that there isn't a way, is this something that can be scripted (after the merge, run the script to select all image frames, set the image size to 100% and then scale the frame to the image).

In my testing, selecting preserve image and frame size and center in frame keptthe frame at the size drawn int the template and centered the image. Unselecting the center image put the image inthe upper left corner, and it either left the frame alone if it was larger than the image, or expanded it (even off the page) if the image was too large. Most images seem to have been imported at 100%. I still can't explain why a handful are coming in at 50 or 25%, but there was a bug discovered a year or so ago that caused image scaling for particular pixel dimensions for one user (might have been a combination of dimensions and resolution) which might explain it. I'm merging into a 20 x 24 page filling nearly the entire page withthe frame, and there seems to be space to place these files at 100% so it's a puzzle.
I haven't seen ay images scaled up...

CS3/OSX 10.5 - data merge directly to PDF

g'day there
i'll ask this question anyway despite expecting the answer "no, use CS5".
in InDesign CS3, when using the data merge feature, is there any way to export the merged data directly to PDF like one would in CS4/CS5, as opposed to merging to a new indesign file and making the PDF from there? i use CS3/CS4/CS5 in my workplace and export data merges directly to PDF when using CS4/CS5, but the machine that i am on 90% of the time has CS3 and my workload has an increasing amount of VDP art which is not just in the hundreds of results, but in the tens of thousands.
to me, the obvious answer is of course to swap machines, install CS4/CS5 on my machine, give the artwork to another operator who has CS4/CS5... but for the sake of this post imagine that these solutions could not be used.
in my situation, i'd imagine that this answer would either lie in a scripted solution or a third party plug-in such as XMPie. Maybe the solution lies outside of indesign and with VDP software which may be available on the EFI Fiery RIP maybe?
any ideas, or should i plead my case to management to pony up the cash for an upgrade? I figure whatever answer there is, money will have to change hands at some point.

Tell management they're going to pay one way or the other.
Bob

InDesign Crashing During Data Merge?

Is anyone having any issues with InDesign CS3 crashing while doing a data merge with Excel? Microsoft had some updates with the Office products and I'm wondering if one of the updates has caused a communication problem between the two?

I do it pretty often using CS3 and csv files. As I recall, a broken network path to the source caused me a problem once.
At what point is the crash? You could have a corrupt file, create a new one and test. Elsewise, there could be a character within the data source. Are you using .csv source files (I do but many, especially Mac users, go with .txt source files).

Data Merge causing rip to choke

Similar Messages

Maybe you are looking for