Skip to main content
Felix Mack
Felix Mack
Inspiring
June 23, 2016
Answered

AE 13.8 lots of random crashes

  • June 23, 2016
  • 8 replies
  • 18468 views

Since upgrading recently, I've gotten lots of random crashes doing various things, as simple as moving a layer around.

The error I get is as follows:

Last log message was: <140735214837760> <BEE_WorkQueue> <5> BEE_Project::TimestampGetNext ZANZIBAR-3: cannot produce timestamp, frozen=0, open=0

.

Setup is:

OSX 10.11.5

Mac Pro (Mid 2010)

The same project files had no issues in the previous versions.

    This topic has been closed for replies.
    Correct answer galxcom

    It seems I have fixed the issue. Now checking but no crashes.

    For me problems was in expressions. They were completely correct and simple (like parenting) and worked just perfect in previous AE version but most likely they cause crashing in 13.8. When I have deleted all layers with expressions – everything stopped crash.

    8 replies

    rostyslavr45874371
    rostyslavr45874371
    Participant
    November 4, 2018

    Same problem when AE trying to autosave the project

    andrew-hsf
    andrew-hsf
    Participant
    April 26, 2018

    I just updated this morning and now I have this bug as well.

    There are so many bugs and crashes now, what's going on AdobeSupport​? Your QC is getting worse for updates. We pay for this so it should work. I'm at work and I've spent the last hour doing nothing while rebooting and looking into this annoying error.

    PLEASE FIX IT ASAP!!!!!

      DBowker3D
      DBowker3D
      Inspiring
      May 3, 2018

      Just started getting the same behavior in AE, especially with some older comps. It's a big project, amny sub-comps but I really need a way to render it out. It's not like you can just undo or re-do a project of this complexity.

      BTW -not running on Mac OS like many on this thread but latest version of Windows 10. So this is an equal opportunity Adobe bug! Everything else is stable and the issue is not on every comp, though even a few is too many for the money we pay for this.

        CarlosPuigGC
        CarlosPuigGC
        Participant
        October 16, 2018

        Absolutely! I have a PC and I have the same problem with big project:

        After Effects error Crash in progress. Last logged message was 11796 BEE_WorkQueue 5 BEE_ProjectsTimestampGetNext ZANZIBAR-3 cannot produce timestamp, frozen=0, open=0

        & After Effect's can't continue sorry, After Effects has crashed. For After Effects Help and Support, go to...


        I could solve my problem with a, Adobe technician simply doing: File > Project Settings > Video Rendering and Effects > Use > Change "Mercury Software Only" for "Mercury GPU Acceleration (CUDA)".

        Hope this works for everybody!

          trashcaneron
          trashcaneron
          Inspiring
          November 13, 2017

          Any work arounds? Curious if you are running High Sierra and CC18. Have seen quite a few bugs.

            Charly10
            Charly10
            Participant
            May 11, 2017

            I had the same problem and fixed it by updating my graphic card driver !

              trashcaneron
              trashcaneron
              Inspiring
              November 12, 2017

              I'm having the same problem here. Exact same error.

              I was working in Mocha AE and copied shape data to clipboard and then it happened. Repeat issue every time. Quitting Mocha and re-launching AE solves it. BUT still unable to bring in my shape data which is infuriating.

              Last log message was: <140735214837760> <BEE_WorkQueue> <5> BEE_Project::TimestampGetNext ZANZIBAR-3: cannot produce timestamp, frozen=0, open=0

                M
                martynk27914441
                Participating Frequently
                November 13, 2017

                I'm having this issue too with Importing Mocha shape data.

                Seems that if the mocha shape data has been copied to clipboard then it insta-crashes After Effects.

                Last Logged message was : <7456><ZANZIBAR Hunter> <5> ProcessFrom MAIN requested_sync, proj=3503

                Or when AE is opened with data already copied:

                Last Logged message was : <1008><BEE_WorkQueue> <5> BEE_Project::TimestampGetNext ZANZIBAR-3: cannot produce timestamp, frozen=0, open=0

                  A
                  adobeckp
                  Participant
                  April 14, 2017

                  I had the same problem. You know how I fixed it? It WAS related to comp size....

                  I had a comp size of 1064 x 2828 and it kept crashing when trying to save a still or just go to the render queue...

                  I changed it to 1100 x 2872 pixels...

                  Problem (for me at least) solved.

                  galxcom
                  galxcomCorrect answer
                  Inspiring
                  August 1, 2016

                  It seems I have fixed the issue. Now checking but no crashes.

                  For me problems was in expressions. They were completely correct and simple (like parenting) and worked just perfect in previous AE version but most likely they cause crashing in 13.8. When I have deleted all layers with expressions – everything stopped crash.

                  H
                  HorstO
                  Participant
                  June 24, 2016

                  I've got the same problem! In my case I was also unable to use some plug ins (Saber) and presets.

                  Szalam
                  Community Expert
                  SzalamCommunity Expert
                  Community Expert
                  June 24, 2016

                  That sounds frustrating.

                  I would highly recommend filing a bug and give as much detail as possible. If you go into your help settings, enable logging, and maybe do a screen capture of yourself working until the bug hits, that would be highly beneficial, I'm sure.

                  Felix Mack
                  Felix MackAuthor
                  Inspiring
                  June 24, 2016

                  I'm in contact already. I switched back to the previous version, and it is stable with the same files. I guess I will stick with that for now...

                  Terms & ConditionsAccessibility statement
                  Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices