When attempting to add a sourceRectAtTime() expression to a Mask Path property that references a text layer, After Effects will immediately crash upon evaluation.

Reproduction steps:
1. Create a new project
2. Create a new composition (tested with HDTV 1080 29.97 preset for repro purposes)
3. Add a text layer
4. Create a comp-size solid
5. Add a comp-size mask to the solid by double clicking the mask button
6. On the "Mask Path" property of the mask created in step 5, add the expression: `thisComp.layer(<name_of_text_layer>).sourceRectAtTime()

After clicking out of the expression editor and allowing AE to evaluate, After Effects crashes.

OS: Windows 10 Pro
OS Build: 19041.572
AE Version: 18.0.1 (Build 1)

Since a couple of updates I've had this weirdest glitch.

On imported RAW images, when the preview resolution is set to anything less than "Full", the layer's gamma suddenly gets waaaaay off.
This only happens if "Linearize Working Space" is checked in Project Settings.
I've also reproduced this bug with .dng instead of .RAF, so the RAW image format does not seem to matter.

Currently using AE 18.1 on windows 10, Camera Raw is up to date and this glitch happens whether GPU acceleration is on or off.
Unfortunately I can't seem to find on which version thig bug appeared, since I do not have access to anything prior to 17.7 and the glitch is still present there.

It is possible to compensate the layer's gamma offset manually, but it's still a major workaround to get the preview working properly.

I have attached two images and also made a small project to show this issue. If anybody wants to look into this, you can simply switch the composition_01 resolution from "Half" to "Full" and the bug shoud be pretty clear.

Here is the project: https://drive.google.com/file/d/1ensmhOuLroMKAdCmpdrynHDOw8J40TjH/view?usp=sharing

Thank you for helping me out!

If you resize the composition using the "Crop Comp to Region of Interest" feature in version 17.5.1, there will be a difference in the display between 2D and 3D layers with the same X and Y numbers.
It didn't happen in versions prior to 17.1.4.

The following reproduction procedure
1, Creating a composition
2, Create a new layer
3, Resize the composition using "Crop Comp to Region of Interest"
4, Check the 3D layer.

Other than "Crop Comp to Region of Interest", the same phenomenon occurs when resizing with "Composition Settings / Advanced / Anchor" selected other than the center.
Also, if you open a project file saved in version 17.5 or later in version 17.1.4 or earlier, the displayed position will change.

The workaround I've found is to place the camera layer to restore the display.

Thank you.

AE CC 2020 17.0.2 Build 26
macOS Catalina 10.15.3 (19D76)
MacBook Pro (16-inch, 2019)
2.4 GHz 8-Core Intel Core i9
64 GB 2667 MHz DDR4
AMD Radeon Pro 5500M 8 GB

There is a glitch that is especially noticeable with the TRANSFORM effect in AE CC 2020. Easily reproducible:
New composition
New solid
Add transform effect
Add rotation keyframe
Add second rotation keyframe further down (1x cycle)
Render

There are random black glitches on rotation. This does not happen with the native transform (non-effect version).

Does not appear to be reproducible with RX580 in 10.14.6.

Issue disappears with Mercury Software Only rendering. Happens with Mercury GPU Acceleration (Metal), which is the only option available on MBP16,1 with native GPU.

Same is reproducible with RX 5700 XT in eGPU in 10.15.3 (19D76).

When will this be fixed?

I have an expression that links to another layer. When you update a Layer name or Property name, then that name is updated in all the expressions that use that name (Extendscript calls this autoFixExpressions).

However, if an expression contains a Try/Catch statement, then no matter what, the names won't update in the expression (almost like AutoFixExpressions doesn't work if the expression contains a try/catch).

I'm not sure how I haven't encountered this before, as try/catches are useful just incase links are broken or are missing. I've posted this to Reddit, asking if this is a bug or a 'just me' issue, but it seems that it happens to others as well.