Skip to main content
G
graham--k
Participant
December 18, 2017
Question

Premiere CC 2018 Crashes Constantly

  • December 18, 2017
  • 1 reply
  • 832 views

Hi, I recently upgraded from Premiere CC 2017 to CC 2018. I've found CC 2018 to be totally unusable, because it crashes within several minutes of opening.

When I open a project file, it begins loading all the files within the project, and conforming certain files as needed. Totally normal behavior. But within 2-3 minutes, when I look at my computer's memory usage, it has skyrocketed up to using 31.9 out of 32GB (even though I have "RAM reserved for other applications" in the preferences set to 12GB). At this point, Premiere starts giving me all kinds of error messages. Literally dozens of errors pop up one after the other, including many that start with "A low level exception occurred"... etc. It seems that Premiere begins eating all of the system memory until nothing can function properly. Any other apps, like Chrome, that I have open will crash, and then Premiere itself inevitably crashes. A few times, it has crashed the whole system and required a hard reboot. On one of those instances, the abrupt crash corrupted an external hard drive's file system and turned it from NTFS to "RAW." Thank god I had that hard drive, full of irreplaceable documentary footage, backed up.

My computer is 5 months old, and has more than capable specs, so this behavior is really unexpected. So far I've been avoiding the new version of the software entirely and still using Premiere CC 2017. But now CC 2017 has started having separate issues using CUDA with my NVIDIA GeForce GTX 1060 6GB graphics card. (just shows a black screen). Will CC18's memory-eating problem/constant crashing be addressed in the next update of CC 2018? Or is there anything I can do to fix this problem until then? Here are my PC's specs:

Windows 10 Home

Intel i7-7700K CPU 4.20 Ghz

32 GB RAM

NVIDIA GeForce GTX 1060 6GB with latest driver (GeForce Game Ready Driver 388.59, released 12/07/2017)

250 GB SSD/1 TB HDD

Thanks!

Graham

This topic has been closed for replies.

1 reply

E
excited_Genie16B8
Legend
December 18, 2017

Changes to Dolby Decoding and Encoding Support

Because of the above, there is a memory leak bug.  You will need to figure out how to conform only a small group of files at a time, closing and reopening PP after each group finishes conforming.

    G
    graham--kAuthor
    Participant
    December 18, 2017

    I'm not using any Dolby audio files in the project-- everything is stereo WAV or MP3 audio-- but do these changes effect how Premiere conforms ALL audio files? What is Adobe doing to address this memory leak bug?

    The documentary I'm editing is comprised of thousands of files from more than 5 months of shooting. Usually I work with a project file that includes only the particular scenes I'm focused on, rather than the "master" project file for the whole film. But even these truncated project files crash my system when I try to load them in Premiere CC 2018. To slice them up into even smaller chunks so that the software only conforms a small group of audio files at a time would result in an incredibly slow and inconvenient workflow just to prevent Premiere from constantly crashing. There has to be a better way to get all this footage conformed and loaded properly without risking a potentially damaging hard drive crash each time. Adobe, any thoughts?

    E
    excited_Genie16B8
    Legend
    December 19, 2017

    do these changes effect how Premiere conforms ALL audio files?

    I've only noticed it with Dolby encoded audio (AVCHD).  My ProRes footage (Uncompressed audio) works fine.

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