Skip to main content
Z
zilber
Participating Frequently
August 2, 2020
Question

Premiere Pro 14.3.1 Memory leakage and more. Can't finish my project

  • August 2, 2020
  • 4 replies
  • 2653 views

 

Discovered issues:

  • Project of 15 minutes with 20+ source footage files loads for 10 minutes after clean boot, no disk activity most of the time
  • Any changes to the project, i.e. adding 53 kb picture leads to 15-20 minutes of 100% CPU load (without any indication of it within the app), when I can't play my program at all. 
  • Can crash out of the blue on any action, such as adding a keyframe to a grafics.
  • Has memory leaks. Demands 75 Gb of Swap space to work with the project, all footage+proxy of which are 25 Gb.

Can not finalize the project now, which was 90% ready 😞 Please help!

Seems like a very first beta of proof of concept, how could it be with your history? 

Now I am really looking forward to migrate to Final Cut Pro. Who needs all those cool and professional features of yours if they are practically unusable? 

Also, may I suggest to run the application once or twice with some QA engineers involved before public release? 

    This topic has been closed for replies.

    4 replies

    R Neil Haugen
    R Neil Haugen
    Legend
    August 2, 2020

    Kevin's got a good response, btw.

     

    What I'm looking at is the Warp being used. If clearing the cache/media cache database files doesn't help, I really would make a new project file, and from the Media Browser navigate to this one and import the objects one by one, to make sure wbich work and find any which don't.

     

    Neil

    Everyone's mileage always varies ...
    Z
    zilberAuthor
    Participating Frequently
    August 2, 2020

    Neil, yes, warp wa used, to stabilise the picture, as I told earlier. And last actions I've made prior to upgrade and all those issues, was adding Warp effect to part of the program and then cutting some of those to pieces. What might be wrong?

     

    And I am really unhappy, that I will have to do the project from ground zero each time I have those issues.

     

    Thank You for your help!

    Kevin J. Monahan Jr.
    Community Manager
    Kevin J. Monahan Jr.Community Manager
    Community Manager
    August 2, 2020

    Zilber,

    Sorry. Is this new behavior, or behavior that occurred after an amount of time or after you updated Premiere Pro? In either case, I would delete media cache with all projects closed. You do so from Premiere Pro Preferences > Media Cache. Again, do this from the Home Screen with all projects closed. Report back with the results.

    If that is still not working well for you, create a new project. Import the sequence(s) into the new project and then check the results. 

    I would also be suspicious of any files created by Nikon cameras as I have seen weirdness with the video files created by the camera brand off and on for years. Transcoding them to a ProRes variant can rid you of that behavior.

    Regarding testing, an FYI: the program has a staff of QE engineers and also is scrutinized with a new public beta of Premiere Pro. Problems of this nature are usually project corruption that occurs from time to time to certain editors for reasons that I just described: bad media, project got updated over major versions, raised system requirements, corrupt media cache for the version.

    Sorry for that. Hope we can get you going again.

    Thanks,
    Kevin

    Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
    Z
    zilberAuthor
    Participating Frequently
    August 2, 2020

    Dear Kevin, thanks a lot for Your advice, I've cleaned all caches as You suggested, however, I still have same issue, right after peak files were re-created. Adding a title to the project takes ages to take effect.

    This problem occured yesterday, after I've made an update, I've tried to use autosave files, but there is still an issue.

    I was working with my Nikon camera at FCP, made hours and hours of video and never had an issue like this. Also I was working with my footages normally at the very same project before, never seen any problems.

    Can You please clarify, what does importing sequence means? should I redo all editing from the scratch? I've just finished to syncronize all my footages and done all editing... I had only titles and few grafics left to do... Does it occurs often in Premiere Pro?  

     

    R Neil Haugen
    R Neil Haugen
    Legend
    August 2, 2020

    One person having an odd issue on their system means the entire app is bad? Wow.

     

    Past what RJL is asking for, what media are you using in that project, what created the media and where is it stored/accessed from?

     

    What effects are involved?

     

    Is this happening if you create a new project and work at something?

     

    Neil

    Everyone's mileage always varies ...
    Z
    zilberAuthor
    Participating Frequently
    August 2, 2020

    Dear Neil, thank You for your rapid response!

     

    To tell the thrust, things happened to my own project are really bothering me and I consider it natural. 

    I agree, the problem is really odd due to the way it appears which is more suitable to an early pre-realease demo, not Pro software.

    Following Your questions:

    1) I use following media types:

    • MOV files with AVC codec 1920x1080@50 from Nikon 5500
    • MTS with AVC codec 1920x1080@25 from Sony MC-1500
    • WAV with PCM codec 48kHz 24bit from Zoom H4n recorder

    All media is stored at Lacie external USB3 HDD, which provides 25MB/s random access, and barely used during hickups of the Premiere.

    BTW, moving media to internal SSD does not change anything 😞

    2) I use only two effects now:

    • White balance (standard tool)
    • Warp Stabilizer (standard effect)

    3) If I open new project, I can work fine.

     Now if i am adding anything to the project, like small PNG image, it can think for 15-20 minutes before it appears at program screen. And this action adds 20-30Gb of memory usage per each image I add (biggest of which is 200 kb)

     

    Thank You very much for Your help.

    R
    RjL190365
    Legend
    August 2, 2020

    Are you on MacOS? You see, if you are on Windows, then you cannot install or run Final Cut Pro at all since that program is MacOS only.

     

    In addition, it would help us forum users greatly if you tell us exactly which system you have - and make sure that you tell us exactly all of the components of that system, including the CPU, GPU, RAM and disks.

    Z
    zilberAuthor
    Participating Frequently
    August 2, 2020

    Dear RJL, thanks a lot for your help!

     

    I am using Catalina 10.15.6, which is latest MacOS version AFAIK, so no big deal to use other MacOS programs other than Premiere 

    CPU is Quad-Core Intel Core i7@2.8GHz

    GPU is Radeon Pro 555

    RAM is 16GB LPDDR3@2133MHz

    I use MS35U3 Lacie 1Tb HDD to store media

     

    Thank You!

    Z
    zilberAuthor
    Participating Frequently
    August 3, 2020

    And should you uninstall Premiere Pro, then there will be no way at all to reinstall the very same version that you uninstalled a couple of years from now as Adobe is now restricting version availability to the two newest major versions of any of its Creative Cloud software. That is what exactly happened to the millions of users who still have systems that are based on legacy or obsolete CPU platforms running on legacy or obsolete GPUs.

     

    At this point, Adobe is so far into the subscription model that the only way to "fix" all the issues is to do what the company itself does not want to do at all: Revert back to the high-priced, one-time-purchase "perpetual license" model. And you will have to pay at least $900 USD up front for the first version (the same as it was prior to Adobe adopting the subscription model) - and even with $150 upgrades available, it will take at least four to five years worth of annual version upgrades just for the total cost of a "perpetual license" to equal that of four to five years worth of Creative Cloud subscriptions. Until then, the total cost will be higher than a subscription.

     

    And even before Adobe adopted the subscription model, Adobe had been limiting the total number of discounted upgrades on a given perpetual license to just two major version upgrades at the discounted price. Once three major versions (the originally purchased version plus two discounted upgrades) had been reached, the user must then have purchased another full-priced license in order to continue using a given Creative Suite program. Adobe discontinued Creative Suite after the release of CS6 back in 2012.


    Dear RjL190365,

     

    I am not complaining about pricing at all, many software vendors are selling subscriptions now, instead of "perpetual" license and this is fine. 

    The problem is, Premier became practicaly worthless to me. It just does not work and nobody is taking care about that, at least not Adobe. In my case, when adding 50kB image is leading to 20GB RAM demand, I just can't afford that, ofcourse this is easy to say, that I should just upgrade my laptop to late 2032 MacBook SuperPro with 32Tb cache and 128TB RAM at 64GHz in order to be complient to tasks for which were absolutely enough to have my configuration just a week ago.

    So let be it, let Adobe work with huge army of users of 16Tb rammed laptops only. I am only having something money could buy, so all I need now is to find a way to cancel my subscription ASAP.  

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