Skip to main content
Known Participant
November 30, 2010
Question

Your computer does not have sufficient memory

  • November 30, 2010
  • 2 replies
  • 2570 views

This problem is already tracked in a couple of other threads but I wanted to start a new one where I have already implemented most of the recommended fixes but am still having a problem. When attempting to publish various projects, and with no particular consistency, I'll receive this error:

Your computer does not have sufficient memory resources to publish your file.

  • I always launch Cp5 as an Administrator
  • I always clear the cache
  • All projects have the following Preferences un-checked: Advanced Project Compression and Compress SWF File
  • I continue to reboot and re-launch until publishing inexplicably works.
  • Once a project is suceesfully published, attempting to do so again usually results in the same error.
  • After receiving the error, and attempting to publish again, Cp5 typically crashes

I am running Windows 7 with a 2.66GHz processor and 4 GB of RAM on a 32-bit system

Please advise on any fixes, solutions, work-arounds, or animal sacrifices that will help me out.

Thanks!

    This topic has been closed for replies.

    2 replies

    Known Participant
    December 2, 2010

    I've been experiencing this for awhile.  It initially only occurred with upgraded (from CP4) files but I have since created numerous from scratch files and the problem still occurs.  I've tried unchecking the compression options as mentioned in this post:

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

    This does not solve the problem.  The error occurs sometimes right after opening the file, sometimes after working on it for an extended amount of time.  It occurs when I try to preview the entire course or just a few slides.  Also, though I've never seen anyone else mention this, if it occurs when I preview and I then try to publish, Captivate crashes completely.  My event viewer has the following event logged when this occurs:

    Faulting application adobecaptivate.exe, version 5.0.0.596, faulting module cpswfgenerator.dll, version 5.0.1.607, fault address 0x00080954.

    This is an exremely frustrating issue since it doesn't happen every time.  I have experienced it with multiple files so I don't think it has to do with any one file.  Also, I have just recently did a clean install (last week) and am still experiencing the problem.

    For reference, I'm using Windows XP sp3 (32bit), 2.8GHz Intel Core 2 Duo CPU, 3GB RAM.

    RodWard
    Community Expert
    Community Expert
    December 1, 2010

    Rather than blame Captivate, this sounds to me like there's something in your project that might be causing instability.

    I was having the same problem on one of my projects many months ago when I was working on the Cp5 beta program.  It turned out to be due to having square braces [ ] in the Slide Notes area.  (This was confirmed by Adobe techs after I sent them the project file.)  Apparently there are some characters that should not be used in the Slide Notes area, especially if you use them in Closed Captioning.  It was the fact that I had accidentally included a Notes line with square braces as a CC line that caused the error.  So I removed all square braces, replaced them with pipe characters, and haven't seen the issue since.

    Some other questions in case the above doesn't work for you:

    • Is this project perchance one that started life in a previous version of Captivate and you upgraded to Cp5, or was it created from scratch in Cp5?
    • Does it do this in just this one project or on any Captivate 5 project you create from scratch?
    • How big is the project?
    • Does it contain any Flash animations that might contain AS2 code or that were published as AS2 (even though they only contain stop() actions)?
    • Have you tried copying groups of files from this problematic project over to a fresh new blank project to see if you can replicate the issue there.  As soon as you see the issue reappear, try deleting out the last group of slides to see if that removes the issue again.  By a process of elimination you may be able to find the actual slide/s that are causing the issue, and then keep deleting items off the slides until you are able to find the actual object.  I've found corrupt objects this way on a few rare occasions that Cp projects became unstable.

    Hope this helps,

    Rod

    December 1, 2010

    Hi Rod,

    Can you share your project which produces this error when published ? Please upload the project to acrobat.com and email the download link to ashwin at adobe dot com

    Thanks,

    Ashwin Bharghav B

    Adobe Captivate Team

    RodWard
    Community Expert
    Community Expert
    December 1, 2010

    Sorry Ashwin, but that was like over 6 months ago. The project no longer exists on my hard-drive. I've also searched Outlook for the original emails about this error but cannot find them.