Skip to main content
Participating Frequently
December 7, 2006
Question

Hanging on a newly recorded project "Save as"

  • December 7, 2006
  • 13 replies
  • 917 views
We've just started using Captivate2 (v2.0.0) however we've already bumped into a repeating serious flaw.

After recording a short web based software simulation (135 slides), we attempted to save the project using the usual "Save As" option and clicked ok.
The file gets created (~7MB) in the target directory, Captivate shows it's saving and the save bar gets to the end but then just hangs using 99% CPU. Using the Task manager process window with I/O read,write and other shown, we can see that no data is read, written or "other". After a while windows changes the title bar to "Not Responding". This doesn't change even after leaving it for 2 hours.

The only option is to end the application.

On attempting to load the saved project, Captivate states that the project is corrupt and then closes - no storyboard is displayed.

The machine is a IBM T42 laptop, 1GB RAM, 10GB free HD space running Windows XP and IE 6.0. The rest of windows XP patches are uptodate. Laptop screen as primary at 1024x768x16bit and the secondary external monitor is at 1280x1024x32bit.

This is repeatable and first occured during a 26MB file (360slide) recording.

Any one else have this experience?
    This topic has been closed for replies.

    13 replies

    CatBandit
    Inspiring
    December 7, 2006
    Hi folks!
    What bug? I don't see a bug here at all. What is missing from the "number of slides" discussion is - everything else. Here comes good old argumentative Larry ... and I don't mean to be, really.

    I've noticed dozens of discussions about large, unworkable files where the only item of discussion is the number of slides in the project. I'd kind of like to get everyone back to thinking of overall demands on resources, as opposed to just "how many slides".

    For Instance:
    NIck's situation is a classic WAD (working as designed). Nick states he has a single Gb of RAM as though that should be sufficient. It's not. In fact it is woefully low for a large project ... because ... there is (only) 10 Gb free on the HDD? 10 GB? Adobe's " Production Studio Premium" requires 21 GB just to install, or 31 GB if you want to include "After Effects" disc caching ... 10 gigabytes is the same as being completely out of space because ...

    ... that leaves no room for page swapping (virtual memory functions), which are needed when physical RAM is insufficent for the working processes. That 1 Gb of RAM is probably screaming for help, and there is none available. Do you notice (hear) signs of "thrashing" when doing anything resource intensive? It is your HDD telling you it is dying while valiantly trying to keep up.

    I don't believe you have found a bug - I think your system is inadequate for the tasks you are asking of it.

    FWIW: A " short 135 slide project" is an great oxymoron. A "short" project is 10-15 slides, and a large one is 60-70 slides - assuming industry averages for physical size and included objects in the movie. A 135 slide project is a short disaster waiting to happen on most older machines.
    .
    Participating Frequently
    December 7, 2006
    Cheers for the bug link.

    I've sent the text from this original post via the bug submission form.
    December 7, 2006
    Hello Nick,

    During production I work with Captivate files with well over 135 slides, granted the final version of the project is much smaller and have not experienced the issues you have kindly listed below, I am also using XP SP2. I would be more than happy to take a look at your file if you think that would be useful. You can send it using the following web address -
    http://dropbox.yousendit.com/macrofireball

    However, if you feel that it would be more appropriate you could to submit this using the Adobe Captivate Enhancement Request and Bug Submission Form. and get somebody from the Adobe Captivate team to look into this for you.

    Regards,
    Mark