I'm not sure what's going on, but this new version has made dragging text or other layers around the screen a ****-shoot as to whether it crashes AE or not. The small silver-lining here (very, very small) is that it saves your project before it crashes with a "1" at the end of your original project name. As a result, I have several projects with a "11111" at the end of the name. FRUSTRATING.

Hard to tell what the culprit is. GPU settings? Other MacBookPro (2016) issue? All I know is that AE 15 in general has been a giant step back in terms of stability for me. What's worse, when I roll back to v. 14, some of those issues seem to have traveled with it. The loooooong save project times that started in v. 15 seem to have gone back to v. 14--which would then seem like a computer issue. I can't figure it out, and it's frustrating beyond belief.

I need the Essential Graphics stuff in v. 15, but the rest I don't need. Have you guys seen anything on your end?

When I start up After Effects 15.1.1 it crashes immediately on my Mac.

There's no way to get around it. I have removed all the CC with the Cleaner and reinstalled and it still does it.

iMac (Retina 5K, 27-inch, Late 2015)
4 GHz Intel Core i7
32 GB 1867 MHz DDR3
AMD Radeon R9 M395X 4096 MB

Process: After Effects [1499]
Path: /Applications/Adobe After Effects CC 2018/Adobe After Effects CC 2018.app/Contents/MacOS/After Effects
Identifier: com.adobe.AfterEffects
Version: 15.1.1 (15.1.1)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: After Effects [1499]
User ID: 501

Date/Time: 2018-05-19 10:49:05.996 +0100
OS Version: Mac OS X 10.13.4 (17E202)
Report Version: 12
Anonymous UUID: 58B44E7F-0E95-BCD8-8E12-A790C2168A2A

Time Awake Since Boot: 1900 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x0000000000000000
Exception Note: EXCCORPSENOTIFY

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

That's not a first time I writing about the problem! After Effects CC 2018 Optimization is just terrible while same Premiere version works great! I'm working with same video file (4K, 29 fps, 1 min length), and AE can't even play smoothly the file on the timeline. In addition, the rendering time (via Media Encoder) is longer X10 than Premiere rendering (rendering settings also are same!!!). All app settings are same and GPU support is on! So when I checked the resource monitor, I see that Premiere uses about 70-90% of the CPU, and about 40% of the GPU. AE is using about 5-10% of the CPU and 2-5% of the GPU. Please do something with the optimization! Thanks.

My system is: ASUS Prime X399-A

                      AMD Ryzen™ Threadripper™ 1950X Processor (16 cores)
                    64G of DDR4 RAM

                    GeForce GTX 1070 8G

We are seeing an intermittent (~1 out of 10 times) crash in our latest releases of Particular (v3.1.1) and Form (v3.1.1) in Trapcode Suite 14.1.1. Crash log and sample project attached.

The crash does not appear to occur in our own code. As indicated in the crash log, it appears that AE is attempting to open a dialog from within a drawRect operation.

We would appreciate any clues as to what our plugin might be doing in its own initialization that might lead AE to post some warning or error dialog from within a draw operation.

OSX 10.13, AE CC2018 (15.1.0, Build 166)

Steps to reproduce (intermittently):
1. Open attached project and select Comp8
2. Select the Solid in timeline window
3. Quickly drag Particular from the Effects & Presets list to the Comp preview

Trapcode Suite 14.1.1 installer is available for download here:
https://www.redgiant.com/products/trapcode-suite/downloads/

MacOS High Sierra 10.13.3, AE 15.1.1 (but I've noticed this in many previous versions as well)

Steps to Reproduce:

• Turn "Toggle Mask and Shape Visibility" on.
• Play the current composition.
• Switch the timeline to another composition.
• Switch back to the first composition.
• "Toggle Mask and Shape Visibility" is now turned off and needs to be turned back on again.

It's mildly annoying and I've noticed this for a long time but only recently discovered what actually causes it. It seems that when you play a composition, it will disable that switch in order to not show layer handles/outlines and such during playback. It will normally re-enable that switch when playback is stopped, but opening a different composition stops playback without re-enabling the switch.