Premiere Pro keeps running in the background using RAM, not able to shut down

Lukas, glad you found a workaround, but you should not be having this problem and it might be worthwhile digging into your setup to see if we can figure out what's going on...    post back if you want to dig into the issue.

I am definitely going to try this, thanks for the explanation!

I think I actually found the cause of the problem with premiere crashing, when I drag the playhead over the timeline! As I said I use .mov footage and it fixed the crashing issues when I removed/deleted the lumetri color effect entirely from the .mov itself. An adjustment layer works just fine with lumetri color! Glad I got rid of that issue..

It might be helpful if you did some googling on mpeg video to understand why this material may be difficult to work with in Premiere as opposed to a format like prores where each frame is discreet.   Proxy workflow allows you to transcode to a format that's easier for premiere to work with.  It's a fantastic way of working with material that Premiere might have problems with.    However, in this situation, it might be simpler to simply convert all your source material to vertical 1080x1920 with the prores 422 codec so that your source material matches your delivery/output specs.   Maybe someone can post the correct workflow for this.  If not, if you can send me a short clip of the camera original, I'll see if I can figure out the correct workflow to do this conversion...  you can send me a direct message by clicking on my username at the top of the post.  Any excuse not to do the work I should be doing.  

Thanks for reaching out Micheal!
I'm only using .mov files at 1920x1088 (don't ask me it's an older Camera, Canon 60d to be exact) and 23.98 fps.

And the sequence settings I'm using are the following. I am editing for IG Reels (in portrait obviously), but I have to rotate the footage by -90°. I'm also using speed-ramps / time remapping or however you call that.

It's in german, sorry..😅

Can you tell me more about that proxy workflow (if the issue isn't related with the above information)?
Text back if you need anything more 🙂

Tiago23782195yo1i, there are lots of things to try and I'm happy to suggest some other things, but it's necessary to approach this in a systematic fashion.  Have you tried the proxy workflow?  Working with heavily compressed media as you are can be problematic.   First thing I'd try is to create a new windows user with administrator privileges and log in to the new account and see if the problem is still occuring.  Do you have anything connected to your computer except for mouse keyboard and external drive?   If so, try disconnecting them.  Try disconnecting from network/internet by either turning wifi of or pulling the ethernet cable.    If you'd like to explain my thinking on any of these suggestions, let me know.  Crazed with work thru the weekend, but will get back to you as soon as possible.  

@Michael Grenadier I totally get you, they really are different. 

Unfortunatly I've tried all the solutions you've suggested to no avail... 

It would be great if this only happened with one project, but it has been happening with all my projects. 

Thanks anyways for all the suggestions, I hope they help someone out there!

Tiago23782195yo1i, unfortunately AE and Resolve are very different beasts than Premiere.   What version of Premiere are you running?  Try installing a previous version of Premiere 23 and see if that makes a difference.    If you have an earlier version of 23 installed, try updating.  You might also try installing the beta version.  If you need help with figuring out the exact version you're running and how to install alternate versions post back.  Not dissing your expertise, just never easy to judge this from a brief post...   You might also try resetting preferences and caches and creating a new premiere project and importing the problematic project into the new project...    

@Michael Grenadier sure thing! 

System: 

AMD Ryzen 9 5900HX with Radeon Graphics 3.30 GHz
RAM 32,0 GB (31,4 GB)

Windows 11 

Asus VivoBook, 64-bit operating system, x64-based processor

Sequence setting differ - it's a 45 minute base project with several different things, but all the media is h264 mp4, 4k 10bit 

Also have animated AE sequences 

My setup really isn't the issue, as I can work much more complex projects in AE and Davinci Resolve. But ever since updating to 2023 Premiere this happens, even with older versions. Everything is up to date now, including graphic drivers. 

Might be a good idea to reset your preferences and delete your caches.   Rendering your sequence might help.  I find the "render and replace" command very useful as it "burns in" the render (although it's simple to "unrender it).    

First, Lukas, what are your source properties and sequence settings?   if you're working with heavily compressed formats such as mp4, or other mpeg variants, particularly anything higher than 1080, 16gigs of RAM may not sufficient.  The workaround is to use Premiere's proxy workflow.  If you need me to go in to greater detail, post back/

Jiaqi5E91, what are the pixel dimensions of your sources and sequence?  Again, 16gigs may not be sufficient so a proxy workflow may be the solution.

and Tiago23782195yo1i, Please tell us your system specs: OS version, Premiere version, amount of RAM, Hardware specs including graphics card and your source properties and sequence settings.

I'm experiencing exactly the same issue to the point where I have given up and do all base edits on DaVinci Resolve, only after do I bring it to Premiere to use AE on projects. 

Right now I've wasted the whole morning trying to finish a 30 second video - it's infuriating!

Hope that by comenting here I'll be notified of any solution!