Weird phenomenon - projects that open with no problem in version 2019 - crashes in version 2020. These are very simple projects. On the Mac they open in 2020, on the PC they don't. I tried to reinstall the software with no external plugins and didn't help. I tried to create a light version of the projects - just one composition - with just one layer of photoshop - still didn't help. Again - this is about a variety of projects, with different sources. i attach a screen pic of the project in AE19 that not open in AE2020. and the PSD
Thank you.

This happens a lot. I use the mogrt and everything seems fine and I render my video from Premiere. Then the layer that has the sourceRectAtTime expression will start jumping around the screen and appearing/disappearing. I restart Premiere, and sometimes it's back to normal, sometimes the jumping around is different. Every render is a surprise.
I've been building morgrts since the start, using these expressions, but since AE 16.1 update, it's been buggy with unpredictable results in Premiere.
Also, if I reopen a comp in Premiere that has a mogrt that uses the responsive time feature, the clip is sometimes missing the outro animation. And I have to set up the mogrt all over again. Before saving and closing there would be an outro to the animation, but it just disappears sometimes if I reopen a project.

I have been working on a project for 10+ hours. It uses nested compositions and expressions referencing between compositions. One of the expressions is a for-loop that runs the sampleImage() expression four times - this expression in particular seems to be causing a lot of problems and throwing "internal errors."

The project has reached a point where it loads fine if all expressions are disabled - the preview updates immediately when I move the time indicator - but as soon as the expression is activated the property color changes from blue to green and hangs there instead of turning red. The preview freezes on that frame and will not update when the time indicator is moved. Other compositions do not update. If memory is purged the preview window becomes empty gray instead of showing a video frame or black screen. In Task Manager, Memory Usage constantly rises until it reaches the cap set in AE.

I've updated to the most recent AE build, graphics card driver, and version of Java, and I've fiddled with memory allocation and Secret settings. Nothing's fixed the problem so far.

Version 16.1.3, Build 5
11GB RAM reserved for AE, 5GB for other apps
DxDiag attached

After Effects memory management is quirky, compared to every single other professional program out there.
Instead of taking what is there, it overreaches all the time, because of the setting "RAM reserved for OTHER APPS".

So if you have 64GB of RAM, but only 12GB free, and you set AE to "let other Apps use 16GB" you WILL DEFINITELY get an "Out of memory" error later with all the associated problems like crashes, lost work and so on.

So if we can't change the memory management, could we, at least, implement a warning at start up like "Seems you already are using too much RAM, please try to free up XX GB of RAM by closing other applications".
And maybe after that, just reserve all the RAM right at the beginning, so other apps will KNOW their boundaries and don't dare growing until After Effects crashes into them.

For a couple of days I've been trying to figure out why every time I was saving my project and then trying to open it again I was getting this error.

"After Effects error: Can’t find requested element “string”. ( 33 :: 0 )"

I thought I might have a bug in some of the video clips I was using, because when I deleted the clips I could open the file.

After installing and reinstalling After Effects again this had no effect.

Getting stressed with an important upcoming deadline I decided to reformat my whole system and began rebuilding my project and reimporting my clips.

When I came to one scene where I needed to use the Rotobrush I discovered the error again when I tried to reopen the file.

I've removed my comp that used the Rotobrush effect now and the project is saving and reopening without any issues.

Hope this helps someone out and saves them hours of frustration and head scratching.