... is what Epson writes for the scanners under OS X. When you start the software, at some point - after the software has been successfully loaded - a message appears that it cannot be started. Of course, it works perfectly. And if you leave the software running and do nothing, the CPU load is enormous - always around 80% of the CPU is consumed by the waiting software. But if you then initiate a scan, i.e., the software actually does something, the load drops to 10%.
What kind of idiots does Epson actually employ in programming?