The surest ways to avoid it are to buy a Windows computer, or revert to much earlier MacOS and software. My own research now indicates that a combination of Adobe software and recent MacOS are most likely the culprits. LaserSoft Imaging has gained over 25 years experience in the development of imaging software. The problem affects manyl printer brands. SilverFast (Canon) is LaserSofts software for Canon scanners.
There is a high degree of certainty in at least one highly knowledgeable part of the industry that this problem is with CUPS, which is common to ALL current Mac operating systems and to Linux systems. Many things change from one system upgrade to the next and they themselves don't know all the ramifications because these systems are so complex, and code is built upon code, particularly for CUPS - the Common Unix Printing System - which has been around since 2007. It has been around for some years now and Apple has failed to solve it. In particular if you were using El Capitan you would not likely encounter it. Perhaps it is new for you because you had not experienced it before. Well, no surprise here (at least for me) because this is NOT a "new problem".
One could blame the printer driver, but then one would be blaming every brand of printer driver that interacts with MacOS - not very likely. The operating system plays a major role in the print pipeline, of which the Apple version of CUPS (Common Unix Printing System) is an important component, and COULD BE, not certain, where the problem is lodged. It does not happen at all with Windows operating systems, and it did not happen with MacOS from El Capitan and backward. It has happened to numerous people as attested on Internet forums - and frequently enough now to me - that it is a real concern. Getting the system back temporarily is a lot of work. When that happens the whole process stops and no prints can be made. Whether from Epson, Canon HP Lexmark or other printers using MacOS, when an image file is sent from the computer to the printer, the error message "Stopped. The term I used is not unusual as the problem is known to numerous users and within the industry, but for a mysterious reason, at least mysterious to me, it doesn't get resolved. Very often, they fix other things in the background that don't get mentioned in a security update.