PHOTOSHOP CC 2014 - Instability and glitches and incomprehensible error messages on MacOS 10.10 Yoesmite

  • 1
  • Problem
  • Updated 3 years ago
  • (Edited)
Photoshop CC 2014.2.2 Release
20141204.r.310 x64
Yosemite 10.10.3
MacBook Pro (Retina, 15-inch, Late 2013, 2,3 GHz Intel Core i7, 16 GB 1600 MHz DDR3, Intel Iris Pro 1536 MB)

- Getting "Error: Error: No such element:186" each time I create a new document
- Crashes too often. Usually when re-ordering layers or moving an elements
- Weird glitches
- marquee tool selection (the dashed line) is displayed wrongly. It's offsetted by few pixels both x/y when zoomed in.
- Strange patterns / broken image when zooming in

Photo of Antti Vesalainen

Antti Vesalainen

  • 3 Posts
  • 0 Reply Likes
  • frustrated

Posted 4 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
The element error is coming from a script or third party plugin you have set to run when documents open.

Without seeing the crash report, we have no idea why it is crashing - but MacOS 10.10 does have more than a few OS bugs that Apple is still working to solve.

Broken image probably means a video driver bug - and MacOS 10.10 has several known video driver bugs that Apple is still working to solve.
Photo of Antti Vesalainen

Antti Vesalainen

  • 3 Posts
  • 0 Reply Likes
I have not installed any scripts or third party plugins to photoshop, so if the problem is in scripts or plugins they have been installed by Adobe. Disabling script events got rid of the error message.

Adobe should do a full rewrite on their software. It's evident there are serious quality issues. Bit rot.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
None of the things installed with Photoshop would cause that error, and other users are not seeing that error. So there is something added or changed on your system that triggers the error - and it is most likely a script or automation plugin.

Most users are not having that many problems - but MacOS 10.10 does have quite a few bugs that Apple is still working to solve, which can cause a wide variety of crashes, artifacts, and odd behaviors. The image redraw problem you show appears to be the known MacOS 10.10 video driver bugs that Apple is still working on. And again, we can't know why you are crashing without seeing the long, detailed crash report.

Also, no, that is not what "bit rot" means.
And rewrites are never the answer: http://www.joelonsoftware.com/article...
Photo of Antti Vesalainen

Antti Vesalainen

  • 3 Posts
  • 0 Reply Likes
"Software rot, also known as code rot, bit rot, software erosion, software decay or software entropy describes the perceived "rot" which is either a slow deterioration of software performance over time or its diminishing responsiveness that will eventually lead to software becoming faulty, unusable, or otherwise called "legacy" and in need of upgrade. This is not a physical phenomenon: the software does not actually decay, but rather suffers from a lack of being responsive and updated with respect to the changing environment in which it resides."

That's what happens with software built gradually over time. You most certainly should rewrite the thing from ground up. The link you posted was from year 2000. A lot has happened since. Look at osx for example. You need a sane, coherent, purpose-built foundation for your platform. It has been unstable since the version they introduced the swf based menus. I assume the fundamental problem, which is causing the production of crappy code, is that you have too many technologies bolted together. Instability is a clear indicator that there is something wrong. It's not just this setup, I've been using photoshop since version 4, so I've witnessed the deterioration.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
So you've got an OS with bugs, and OS video card drivers with bugs, but blame those well known problems on software that has been continuously refactored and updated - by claiming that somehow working code goes bad over time.

Photoshop has never had SWF based menus. I really have no idea where you got that idea from.

And despite being an old blog post, the logic still applies - and in the intervening years even more evidence has shown that rewrites are a horrible idea.