Hi @Abambo, So I have a question here, you say no application is capable of making a system crash, however, after almost a year of analyzing my Activity Monitor, my Adobe applications are indeed crashing my system. Nothing similar happens when using my computer with no CC applications open (even when they may be running on the back end because CC is always running). This being said, I have spent 20+ on the phone with people from Apple looking directly into my system and doing everything in their hands to figure out the issue, it always comes back to one or several Adobe applications causing too much stress on the system. This diagnostic comes from over 10-12 different people at Apple, this is regarding their system, so not evaluating Adobe. Now, I am trying to understand one thing, you say, "Just to say: crashing the system is different from an application that crashes. If an application crashes, that may be an indication of bad programing too." please help me understand the difference behavioral examples would really help me understand this better. So if I look at my activity Monitor, when I try to do extra simple things like placing a regular-sized image in a book I'm designing (broken into chapters so each file isn't huge), I get the spinning wheel, if I'm lucky the spinning wheel will go away a few minutes later and the image will make it to my file, most of the cases the Application shows as "(not responding)" on my Activity Monitor, which then needs to be forced quit or just wait longer (I've waited over 20 mins). This is an example with placing an image but I have many other examples of getting the spinning wheel while trying to do something super simple like moving a text box. So I'm trying to understand with this example, what's crashing? Is this the system crashing, or is this the application crashing? I also have clear examples of the application crashing, it literally just vanishes out of my screen and a few minutes later I'll get an Adobe Message saying the app crashed and needs to restart and recover files. This one I know it's the app, but on my previous example, what's crashing? And how do I deal with it? Some perhaps relevant context: I don't do anything extremely crazy, I don't design large files such as billboards or heavy data images, most of the times I'm working on simple vectors for branding and presentations and publication on InDesign, some minimal photo editing on Photoshop. I have used the Mac+Adobe combo for 11 or 12 years now, I've ranged from Mac Book Pros to Mac Book Airs and now back at Pro, it's only in the last year or so that this has gotten extremely painful. More specifically in the last 3 updates from Adobe and the last 2-3 of Mac (sorry I forget the exact names) I am currently on Mojave.
... View more