Your computer does not have sufficient memory

[charliemullin]

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!

[RodWard]

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

[Guest]

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]

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.

[Guest]

Hello All,

Im still facing the same problem right now. Im using Captivate 4, I remember posting at other thread regarding this issue but no clear solution yet was ever mentioned.

I followed different suggestions from others, by creating a new blank project, check "characters" that might have caused the issue, copy the slides into a new project and so on but none of them seem to work.

Now Im wondering if this has something to do with size of my Cp project,with mine its around 170MB.

Really looking forward to possible good feedback on this particular issue.

-Miguel

[Lilybiri]

Hi Miguel,

Certainly for CP4, 170MB is IMO way to big, really. Is it not possible to split the project up in smaller projects and use daisy-chaining?

Lilybiri

[Guest]

Lilybiri,

As what I expected, you'll say the same as what I thought about the size.I have also recommended that the project be split into parts, but unfortunately it was overruled so last night I spent extra 6 hours with this, leaving me at least 4 hours sleep and at some point I was able to published it.I was surprised when I saw there was indeed a published output, and oh yeah the output seems working the way it should.

But due to trial and error approach I forgot the steps I did to produce the output.

I will try to negotiate to them again today regarding splitting the project.
Have you by any chance encountered the same problem with any of your projects?Or will I encounter the same problem when I use Cp5?

-Miguel

[Guest]

Rod,

I was very interested to read the part of your thread where you say using [ square brackets ] in notes/closed captions caused a problem in Cap 5.

Can you...or maybe someone from Adobe reading this message... list down all characters that should not be used in Notes or CC, for both Cap v5 and Cap v4.

I have people using both versions and they need to be made aware of this potential problem.

Many thanks,

Noel

[RodWard]

Noel,

The square bracket character was the only one that I encountered a problem with.  But it's possible that there are others.  Remember I said that this happened when I was working as one of the BETA testers that Adobe invited into their Pre-release program for Cp5.  So it's also possible that the issue was resolved before the product eventually shipped.

Either way, I DO remember seeing this error, and that was the reason.  But it was only when the square bracket character ended up in a line that was selected as CC text.  I have the practice of using quite large characters for CC text (Verdana 20 point) because I figure that people needing CC text to understand the dialog might also find it difficult to read fine print flashing past them on the bottom of the page.  But I prefer to have only one CC line at a time appearing, so at 20 point text you need to know where the line of text will end.  So I used to set up a dummy line with just hyphen characters enclosed by two square brackets at each end and place one of these lines on each slide in the Notes area as a visual guide to how many CC words I could fit on a line before I had to break to another line.

I'd never noticed this error until one day I accidentally ticked one of these guide lines to end up as CC text.  Then all of a sudden I was getting this weird error message.  I sent the project to Adobe and one of the programmers looked under the hood and told me what had caused it (in my case).

It may not be the cause of the issue for the original poster here, but I thought it worth mentioning.

Rod

[Guest]

Hi Rod,

Thanks for taking time for a detailed reply.

All understood.

Thanks again,

Noel

[charliemullin]

Rod:

Thanks for your thoughtful and useful suggestions. I'll investigate further next week but let me answer some of your questions:

• 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?

It's possible that some of this project did actually start off in Captivate 4.

• Does it do this in just this one project or on any Captivate 5 project you create from scratch?

I think that this also occurs in Captivate 5 projects I develop from scratch but I want to test further to be sure.

• How big is the project?

This particular project is several regular slides plus 40 random question slides pulling from a pool of 70 questions. The project is just under 4 MBytes. But other smaller projects also exhibit the problem.

• Does it contain any Flash animations that might contain AS2 code or that were published as AS2 (even though they only contain stop() actions)?

There are some small animations and some widgets all AS3. None of the widgets or animations use stop() actions -- I don't think. But I realize something there could be suspect so I'll have to investigate further.

• 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.

This is clearly the best way to troubleshoot this but my real challenge is the inconsistent behavior. If I can get a project to publish without error, say, ten times, then I would probably declare it to be clean.

I'll let you know what happens.

Thanks!

Charlie

[4madhats]

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.