Skip navigation
rontiara 82 posts
Jul 2, 2009
Currently Being Moderated

InDesign CS4 crashes when I export for epubs

Jun 4, 2011 10:26 AM

Every time I choose "Export book for digital editions...." in the book menu, the program sometimes (but not always) exports to the epub format -- but then InDesign crashes and closes.  Sometimes there is an epub saved; sometimes there is not.

 

This is the error message I get:  "Runtime error:  R6025 - pure virtual function call".  Makes no sense to me, and it happens every time, no matter what other programs I do or do not have open.

 

I'm running Win XP SP3 and have plenty of memory.

 

Thanks.

 
Replies
  • Currently Being Moderated
    Jun 4, 2011 1:59 PM   in reply to rontiara

    Try restoring InDesign's preferences:

     

    http://forums.adobe.com/thread/526990

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 4, 2011 2:57 PM   in reply to rontiara

    This is a generic windows error and is related to some configuration problem, most likely. I suspect the easiest way to cure it is to uninstall and reinstall ID.

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Jun 4, 2011 7:38 PM   in reply to rontiara

    Yes they are!


     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 18, 2011 6:15 AM   in reply to rontiara

    Well, you could go read through http://indesignsecrets.com/guide-to-interpreting-indesign-crash-report s.php.

    If you upload the Dr. Watson log to http://pastebin.com/ and post a link here, I'll take a look.

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 18, 2011 11:09 AM   in reply to rontiara

    I'm not sure I'm doing this right; I've never used Pastebin before.  But the name of the file I uploaded is "rontiaraDrWatson"

    I don't think that worked. Searching for that doesn't work...normally you should get back a URL which you

    can paste here.

     

     

    Quite frankly, I'm not as worried about the crashing as I am about the TOC and metadata problems.  ID seems to save the epub all right before it crashes -- but it will not let me use the TOC I've set up, and there is no metadata in the epub.  This has just started; I used to be able to use the TOC associated with the book, but now it's not even an option when I export to epubs.

     

    I make my living doing this and I have three clients waiting for me to publish their epubs!  Please help!

    I was focusing on the crsah, those are a little more concrete. Your problem is document-specific? Have you tried exporting to IDML and opening the IDML?

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 18, 2011 7:18 PM   in reply to rontiara

    Yes, that's easier.

     

    As for exporting to IDML, that seems to be a document-specific option, and I'm working with books.  Actually, I have three books I'm trying to export to epubs, and they all do the same thing:  neither the TOC nor the metadata export to the epub format, and ID crashes when I export anyhow.  So it is definitely not document-specific.

    No, that definitely does not mean it is not document-specific.

     

    It can happen with all of your documents and still be document-specific. The question is whether, creating a new document from scratch and not importing anything from your existing documents, you would replicate the problem.

     

    In order to figure out what's going on, you're going to have to divide and conquer. Export a pair of your documents to IDML, re-open them, and make a new book. See if you have a problem. If not, keep adding more documents. Until you find the problem or succeed without it. That's how you should proceed.

     

    As for your crash report, well, it looks like your stack is corrupt or non-useful:

     

    *----> Stack Back Trace <----*
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Program Files\Adobe\Adobe InDesign CS4\Required\DOCUMENT ACTIONS.RPLN - 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    ChildEBP RetAddr  Args to Child              
    0012f980 0a171dc8 00000001 00000e02 16dc2de8 0x0
    21c736b0 24da05b8 21c883e8 006c0001 21c157f8 DOCUMENT ACTIONS+0x1dc8
    222fc128 21c736b0 00000000 00000000 00000000 0x24da05b8
    223a6d80 222fc128 00000000 00000000 00000000 0x21c736b0
    223b7ab0 223a6d80 222c78b0 00720001 223e3b20 0x222fc128
    221b49d8 223b7ab0 00000000 003a0043 0044005c 0x223a6d80
    221b68e8 221b49d8 00000000 006d0075 00000000 0x223b7ab0
    221c8690 221b68e8 00000000 006d0075 00000000 0x221b49d8
    221aea80 221c8690 00000000 006d0075 00000000 0x221b68e8
    2204a008 221aea80 00002c01 2228d840 00000000 0x221c8690
    

     

    All we can see is DOCUMENT ACTIONS, which is not so helpful.

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 19, 2011 4:58 AM   in reply to rontiara

    Good morning (for me, at least). OK, let's try to catch up.

     

    I am still not 100% clear what your actual problem is. Perhaps you can start by restating it clearly and unambiguously.

    Has it changed since June?

    You might post a screenshot of the way you have the TOC set up.

     

    But the first step is to figure out if it happens with a brand new document that is untainted by your existing document. Perhaps something in your current document is making InDesign misbehave. So make sure that TOC export works right from a fresh document.

     

    After that, then the task is to figure out what about your document is causing the problem. Exporting to IDML is a good step to clearing corruption, but is not 100% definitive. But if it works, great. Other steps including using the Pages (panel) > Move Pages function to move pages between documents, and also exporting individual stories to InDesign Tagged Text and then re-importing them into new documents. You can also export some items as snippets, though this is likely to have the same effect as IDML, but somewhat more self-contained (think "IDML Export of this page only.")

     

    In short, this is Divide and Conquer. The problem could be in a story, in a style, on a page, in an image, etc., etc.

     

    Additionally, you might want to consider ponying up $40 and engaging Adobe Support: http://adobe.com/go/supportportal.

    Unfortunately support for CS4 is somewhat waning (it is 3 versions old!), and Adobe Support is not always stellar at solving problems quickly. Still, they are an option to consider.

     

    Also, I'm definitely not an EPUB person. Hopefully when you post the details of what exactly you're doing some of the EPUB folks will still be paying attention to this thread and can point out any obvious issues they are aware if ("Hey! It's a known bug if you use the letter é in your EPUB TOC! Just remove it and you're good!" or whatever).

     

    You ask:

    Do you know what I can do to fix the stack problem?  Is that an Adobe problem or a Windows problem?  I'm waaay beyond the limits of my expertise here.

     

    It's not a "problem" per se -- the stack is a data structure that stores state about functions calls made by programs. Under normal circumstances, when a program crashes -- that is, when the operating system detects that a program has done something it should never do, such as tried to access a region of memory that does not belong to it, the operating system forcibly terminates the program -- the stack reflects information about the function that was currently executing, and the function that called it, and the function that called it, etc., etc., typically 20-50 levels deep.

     

    Depending on exactly why the program faulted, sometimes this information is not available. For instance, if the program failure that caused the crash involved corruption on the stack.

     

    Often the stack can give us useful clues about the nature of the crash, and those clues can help us avoid the crash. Simple example: "Oh, this crash is related to the third party extension Frobozz Magic Font! Turn it off!"

     

    I just posted a question about the corrupted stack in the Microsoft forum, and they replied only Adobe can fix it.  It's apparently not a Microsoft problem.

    They are, to a first order, correct. When InDesign crashes, it's an Adobe problem. The stack issue is a low-level diagnostic and is unlikely to be a real problem. But certainly no one could fix it without altering the InDesign program, and only Adobe can do that.

     

    I'm getting pretty nervous about this; I have clients screaming for their books, and I'll have to refund some money if this isn't solved.  Whatever you can do would really be appreciated!

    I think you need to present us with a lot more information about your problem.

    Precise steps to reproduce it.

    Screenshots showing how you have it set up.

    Copies of files that exhibit it.

     

    That we can try to reproduce it, see if it is specific to your machine or your document, give recommendations on how you can work around or avoid it, etc.

    And seperately, aside from all of those things, is getting the problem fixed. Though if it happens in CS4 and not in CS5.5, well, then it's unlikely that a fix will be forthcoming. Adobe just isn't updating CS4 any more. They're hardly updating CS5 and CS5.5, and CS6 is on the horizon.

     

    Oh, and if you're willing to throw money at the problem, you can look at upgrading. EPUB support has changed dramatically in CS5.5 (for the better, I am told, but I don't speak from personal experience), so it's likely that any problems you saw with it under CS4 will be very very different [and hopefully gone!] in CS5.5.

     
    |
    Mark as:
  • Currently Being Moderated
    Oct 19, 2011 5:30 AM   in reply to rontiara

    rontiara:

     

    I'll try to help you.

    I pass for the same problem, but I discover that the problem just occurs in the files that contain symbols, strange symbols in the text.

    Some (hyper)links that comes with the text editor, like M... Word.

    I resolved the problem finding them and deleting.

    Not confunding this hyperlinks with the hyperlinks that you created in ID. But is the key to resolve the question.

    I hope resolve your problem.

     

    Wagner

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 19, 2011 2:28 PM   in reply to rontiara

    BTW -- from reading in the forum, it's my impression that a lot of people have the same problem with CS5

    That's not the impression I have had. I don't recall seeing this particular EPUB problem. Can you offer a link to someone having the same problem? Also, note that CS5 and CS5.5 are not the same, especially with respect to EPUB.

     
    |
    Mark as:
  • John Hawkinson
    5,572 posts
    Jun 25, 2009
    Currently Being Moderated
    Oct 19, 2011 9:50 PM   in reply to rontiara

    I have included the latest crash report in drwtsn32.log in a folder which you can download from my website: www.jonnianderson.com/InDesign.  There are also some screen shots in that folder.

    This link, i.e. http://jonnianderson.com/InDesign does not seem to work. I tried a number of case variations, none of which worked.

     

     

    I tried what you suggested, opening a couple indd files from one of the books that had crashed.  I exported them to IDML, then opened those, renamed them, and set them up in a new book.  I had exactly the same result:  I could not use the TOC associated with this book, and ID crashed when I exported to epubs.  These files are in the IDMLtest folder in the InDesign folder on my website.

    Do they work when they are not in a book?

    Anyhow, if the IDML didnt work, next step is to Move Pages, and if that doesn't work, then export individual stories.

    you've gotta narrow down the source of the problem.

     

    I truly wish there were an alternative to this program.  I've about had it.  And I'm reluctant to invest in an upgrade without some sort of guarantee that I won't have the same problems.  I think you can understand my feelings; I don't trust InDesign any more.

    Well, you can try the 30-day free trial of CS5.5.

     
    |
    Mark as:
  • Currently Being Moderated
    Nov 12, 2011 7:57 AM   in reply to rontiara

    Just wondering, did 5.5 work for you? I have been having a similar problem, but it is happening with 5.5. Very frustrating, I have tried everything. I found the chapter that was causing the problem, have tried several different edits, it is still hanging the program on export to epub.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points