4 Replies Latest reply on Jul 26, 2017 1:47 PM by Kevin-Monahan

    Crash when preview.

    marb

      Hello. Anybody know how to solve this problem? When doing preview, AE will freeze and crash.

      My environment is macOS Sierra version 10.12.5 on MacBook Air mid 2011. CPU 1.7GHZ intel Core i5, memory 4G 1333 MHz DDR3, Graphics Intel HD Graphics 3000 384MB. AE version is CC2017.

       

      When I drag on timeline bar, it shows every frame. But when I click and start preview triangle button, previewing starts and Mac spinning rainbow circle also starts. Previewing loops and doesn't stop even I click space bar or esc key, so on.

       

      And when I see "force quit application", I know AE crash.

       

      Probably something related to OPENGL or anything else???

       

      Thank you.

        • 1. Re: Crash when preview.
          Dave LaRonde Level 6

          You're trying to run AE on just 4 gigs of memory?  That's your problem right there -- you need 8 gigs to get it to run right, and it's a lot better to have 16.

           

          It really does help to check out the system requirements before you just assume a poece of software is going to work, y'know.....

          • 2. Re: Crash when preview.
            marb Level 1

            Thanks Dave.  I agree with my MBA 4g memory is too small.  However, sorry I did not write down this, my friend's iMac shows same freeze problem when reviewing.   That iMac has mid 2010 3.06 GHz Intel Core i3, Memory 16GB 1333MHz DDR3, Graphics ATI Radeon HD 4670 256MB.  Memory 16GB could be enough.  Probably Graphic memory 256MB is too small?

            • 3. Re: Crash when preview.
              Szalam Adobe Community Professional & MVP

              Your graphics memory shouldn't matter.

               

              How long is your composition?

              What is in your composition?

              • 4. Re: Crash when preview.
                Kevin-Monahan Adobe Employee

                Hi marb,

                Are you still facing this problem? If not, let us know how you solved it. If so, please let us know so we can assist you further.

                 

                Thanks,

                Kevin