Skip to main content
B
BernieMaxx
Inspiring
July 21, 2006
Answered

Crash on Publish

  • July 21, 2006
  • 6 replies
  • 768 views
I've been having a great deal of trouble lately when publishing my movies. After the swf file has been created and captivate is supposed to update the cp file, Captivate shuts down completely. Now it has gotten worse, where my last movie will not open. Captivate acts like it's opening it (progress bar advances), but then it goes back to the main menu. When I try to close Captivate, it prompts me to save the file. If I click yes, it hangs up. If I click No, then it shuts down. When I open a new project and try to import the slides from the crashed movie, it will open the movie and show the slides, but each one shows to import to slide 1 and it is ghosted so I can't change it. I tried importing a single slide and again it acts like it is importing, but the slide never appears in the list. I tried searching for this issue in the forums, but couldn't find anyone else that had this problem.
    This topic has been closed for replies.
    Correct answer BernieMaxx
    Looks like that was the problem. I opened up an existing movie using the current filename (9s3_0065_en_SupplierBasics.cp), and after publishing, captivate shut down. I renamed the file to just 0065_en and published it with the same name, and it work perfectly! Thanks guys!

    6 replies

    B
    Bease
    Participant
    August 3, 2006
    Users in my group have had the same issue with Captivate automatically closing after publishing. It seems to happen randomly. Our file names are more than 8 characters so I tried shortening one but it didn't make a difference. We are experienced users with fairly high-end systems.
    T
    terrence_wood
    Participating Frequently
    August 3, 2006
    If the crash on publish is related to the buffer overflow bug, then it is the length of the path + filename that triggers the bug, not the filename by itself.

    Randomly, I have had files which I cannot open for editing. Duplicating the file on disk, opening the copy, and deleting the unopenable original has always worked for me. That said, I have not had any cp files become completly corrupted ("knock on wood" for the superstitious amongst us).

    On high end systems: IMO a healthy amount of video ram, rather than the clock rating of the CPU, seems to make Captivate perform better.
    P
    PeterVaskess
    Participant
    August 2, 2006
    I have a somewhat similar problem. A captivate project that I cannot open to edit.
    The file name/path is not an issue as it is on a local drive, is quite short and there are other projects in the same folder with longer names that work.
    One difference between this project and those others is that the .cp file is quite large at around 10MB - the project is only around 8 frames with audio.
    It published fine originally (few days ago) and I can run the .swf OK.
    When I try to open it the loading timeline runs, there is no complaint or error message but the project does not appear - we stay at the captivate opening screen, the project file name appears in the status bar and in the title bar but I cannot actually get to it to view or edit.
    When I try opening a blank project and importing it, the import actually shows all the slides, lets me go through the motions of importing one or all of them but again, nothing appears.
    I guess that the project is corrupted somehow but I don't want to have to start all over.
    Does anyone have any ideas?

    Regards, Peter
    CatBandit
    CatBandit
    Inspiring
    July 24, 2006
    LOL! I agree with the diagnoses, but differ with your "easiest workaround" part, Terrence!

    My "easiest workaround": Use 8:3 filenaming conventions and work only from drive C:\.

    B
    BernieMaxxAuthor
    Inspiring
    July 24, 2006
    The filename thing could be why it crashed alot, but with recovery. I have to use a Perforce directory structure on my machine, so the path is pretty deep. Publishing to my "c" drive wouldn't help cause that's almost full. With almost all of my movies, they would normally publish fine, but before the "view" button appears, it would shut down, so the movie "time" never gets updated. Moving everything to the "d" drive solved most of those issues, but this was the first time I was unable to reopen the file.
    B
    BernieMaxxAuthorCorrect answer
    Inspiring
    July 28, 2006
    Looks like that was the problem. I opened up an existing movie using the current filename (9s3_0065_en_SupplierBasics.cp), and after publishing, captivate shut down. I renamed the file to just 0065_en and published it with the same name, and it work perfectly! Thanks guys!
    T
    terrence_wood
    Participating Frequently
    July 24, 2006
    It could be the buffer overload bug. Captivate will crash when trying to publish files where the filename and path excedd 128 characters.

    Easiest workaround: map a drive to the folder you wish to publish to.
    CatBandit
    CatBandit
    Inspiring
    July 24, 2006
    I have no idea in the world why, but in 5 years or so (counting the "RoboDemo" days) I can count on the fingers of one hand the number of times the program has crashed, and I have never uninstalled and reinstalled unless I was upgrading to a new release. Yet others seem to find these issues over and over, so I've just assumed that some systems are more fragile than others (although I've been through 4 or 5 different machines during the above time-frame . . .).

    I'm certain that Adobe is concerned about any issue that causes systems (or Adobe's own applications) to crash. Whether or not the problem is affecting enough customers to put it on the panic list is a question to which I have no answer. At best, it is problematic.
    CatBandit
    CatBandit
    Inspiring
    July 23, 2006
    Sounds like (1) you might have created a file that is larger than your system resources can now open, or (2) something in the project has become corrupted.

    I doubt it will make you feel any better, but lots and lots of (mostly new) users have seen this problem. Check your build number to be sure you have the latest build (release). Click "Help > About" to see the version information. The latest English language version should be version 1.0.1, Build #1418. HTH!
    B
    BernieMaxxAuthor
    Inspiring
    July 24, 2006
    Thanks Larry. The file was only 87 frames. My boss was able to import the movie into a clean demo, which I was unable to do. But it only imported the first 79 frames, so I had to recreate the last few. I am aware of the resource issues with captivate and I have reinstalled it to my "D" drive which has 30G free and also relocated the temp folder. One thing I have noticed is whenever I have a crash (happens a lot on captivate), I can usually recover by an uninstall/reinstall. Is Adobe going to address this?
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices