After upgrading to 13.0.2, I am continually experiencing a major memory leak issue. When I have one project open in particular (a large feature doc with hundreds of hours of footage, linked proxies, etc.) upon opening the Memory usage by Premiere slowly balloons to extremely high levels. In Activity Monitor I can see 'Compressed Memory' slowly building to the point of 140 or 150 GB (I'm on an iMac with 64GB of RAM), and 'Real Memory' also slowly building to its limit. Then at some point I get an error that "your system has run out of application memory" and have to force quit.

This happens without any user activity in Premiere, even if I just open the project and let it sit there.
I have tried a huge range of things to diagnose this, including clean installs of PPro, trashing preferences, booting into a clean admin account, using other machines, etc.

Yesterday I reverted to 13.0.1 and was able to get through the day. However I have now realized that the "Clips imported from XML, AAF, prproj, or any other project are not referenced correctly" bug makes that version unusable for what I'm doing now. Seems I'm left with a choice to either have a functioning program OR have functioning clip references. Ha! This is incredibly frustrating and has cost me days of work already.
Happy to get any more info or screencaps to you if there's someone who can work with me to fix this. Thanks.

Clip Markers have a major BUG.
I'm using markers to select the various good sections of footage between a clip. Each maker then is an option.
In my edit in the timeline I use only one of the options marked with a marker.
If I decide later to choose another option (another section of the clip that has been marked) and do a replace edit, then all the markers in the clip move. Basically you loose all your tedious work of adding markers to your clip.
All the markers move and now they don't align with the actions or sections of footage that they are supposedly marking.
This is a big bug that makes clip markers use less. Now we can not trust doing replace edits because it changes all our clip markers.
Please Adobe, fix this issue with clip markers.

In reality, the premiere is a nice piece of software, but in big projects, it becomes a nightmare. Premiere become unstable, unusable slow and sometimes just corrupt save file and hopefully, you have some older back-ups. I work with it more than 15 years - and every year has new surprises, but don't see progress in the right direction.

So I like all new advancements, but I can live without all Team Projects things, and all other ****, I just need stable fast software what will do a job, if I have 400h documentary material, it becomes a nightmare, I can buy latest Treadriper, 4x RTX20Ti etc nothing will help my performance, premiere just don't utilize all available resources.

So if Premiere right now is unfixable and rotten from the inside maybe then make CS6 2020 edition?! idn... I just hope that Somday Adobe will realize Premiere (Stable and fast edition) that is the biggest advancement of all, yes i use stabilizer every day, yes I'm using lumetri colors and yes im using all cool stuff (except all audio filters, because they are unusable) that all is cool, but most important in the end is Stability And Performance - I would love to see 100 usage on my CPU, GPU, and Ram

Any action that spawns an Explorer window can cause Premiere to permanently freeze. It will never recover, and must be shut down through Task Manager. These actions include:
-File > Save as...
-Clicking the OUTPUT name in the Export Media window.
-Clicking "browse" on the Export Frame dialogue box.
-Even hitting the little "setup..." button on the Image Matte Key effect.
-Using Explorer rather than Media Browser when relinking footage.
-Double clicking a blank area of a bin
-And many more.

This has happened to me in Windows 10 and 7.
(Doing "Reveal in Explorer" does not cause this freezing, since that kind of Explorer window is not a save/load dialogue box that is tied to the program.)

This is the most devastating bug I've ever encountered in Premiere. It happens to me a few times a day, and has wasted a huge amount of my time, and my team's time. To me, it is inexcusable that Premiere cannot do something as simple as a "Save As..." without freezing.

Here is a forum thread on this bug: https://forums.adobe.com/message/9696942

This is unique ID# 508 on my Premiere problems spreadsheet:
https://docs.google.com/spreadsheets/d/1dVJb7kI_ZETLavrplfARgn9gL8HUpvkq6A0jCPxqA3w/edit#gid=1133868629

This is a mashup of two posts from the community forum:

Loading RED footage into the source window is constantly crashing Premiere for me.

Currently running:

Core i7 7820x @ 3.60GHz
32 GB Ram
GTX 1070

The Red footage in question runs no problem in Media Composer, Red Cine-X Pro, and DaVinci Resolve Studio at a full debayer in real time. Most of the footage is either UHD or full 4K at 23.976fps. I'm cutting a feature and this issue is preventing me from finishing and may necessitate a move to Avid.

When the RED footage is in the timeline there doesn't seem to be any issue. I've tried troubleshooting for several months doing all of the obvious steps with no luck.

Update:
So after months of trying to figure this out I just had a breakthrough moment:

99.99% of the time I will double click on a clip to load it into the source window. I just happened to click and drag a RED clip into the source window, which I never do in Premiere but sometimes do when working in Avid. For some strange reason I can't quite figure out, all of my RED footage loads and plays in the source viewer when it is dragged into the viewer.

But Premiere will still crash if I double click on a RED clip. This project also has a lot of Alexa, Varicam,and GoPro footage in various sizes and frame rates all working flawlessly. So the problem isn't gone, but it appears I have a workaround for now.

My fear though is that this will only be temporary, as I was editing the RED footage will no issues until this problem suddenly arose. It has nothing to do with program versions or drivers as far as I can tell. Just that after months of using the footage with no problem it was suddenly breaking Premiere.

If anyone can shed more information on the problem it would be very helpful as I can't narrow down what the issue is.

There are a few issues with CC2019 on Windows 10:

1. It randomly uses all of the memory on the computer when loading media during project open and at other random times, often going to 100% even though the memory setting in PPro is set to only use 1/2 the available RAM. Minimizing the main PPro window usually has the immediate effect of memory dropping back to 50% usage.

2. The video stops playing back, whilst audio continues to play. When stopping playback, there is no way to resume playback as the space bar and playback buttons become inoperable. This can be fixed by changing the audio hardware settings and toggling the input device from microphone to none and then saving. This seems to be more prevalent on hardware with more than one sound card (for example I have an external USB Sound Blaster on my laptop).