Zooming in photoshop bug

So my photoshop CC is crashing when i try to zoom. It's not doing this consistently usually whilst I am working I'll try to zoom out and suddenly 'Photoshop CC.exe has stopped responding.
The image that i have inserted or more importantl the the overlay of the red lines keeps popping up whilst zooming. Only whilst zooming again not consistent sometimes the red lines appear sometimes they appear about 4cm around the left and right edges of the image. Anyone know whats happening?

Might be a video driver issue. What happens when when you go into Preferences > Performance and uncheck Use Graphics Processor?
It's usually suggested you update your video driver from the manufacturer's site. (Intel,ATi,Nvdia,etc.)
Gene

Similar Messages

Photoshop bug report site is broken (using wrong site)

I have a pretty serious Photoshop bug to report -- something that was supposedly fixed in 14.2.1.
I took the time to go to https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform as usual when reporting bugs.
I wrote out the nature of the bug, and all the steps to reproduce it.
But the CONTINUE button is non-functional. At the moment it is IMPOSSIBLE to report bugs to Adobe.

Hi,
We ask that bugs for Photoshop get reported here now:
http://feedback.photoshop.com/photoshop_family
I'll take a look at your other thread about pasted AI files.
regards,
steve

Problem with zoom in Photoshop CS6

Hello
I've got problem with new(?) feature in Photoshop CS6.
When I'm working on my project and have for example 150% zoom and I want to move workspace with SPACE+LMB.
In my previous version (CS3) I can do this without problem but know Photoshop shows me my file with FIT TO SCREEN zoom and some frame to choose
which screen area I want to zoom in.
It's just zooming out to full view of file. I hate this, but I can't turn it off.
My system info:
Adobe Photoshop Version: 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00) x64
Operating System: Windows 7 64-bit
Version: 6.1 Service Pack 1
System architecture: Intel CPU Family:6, Model:5, Stepping:5 with MMX, SSE Integer, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Physical processor count: 2
Logical processor count: 4
Processor speed: 2660 MHz
Built-in memory: 3828 MB
Free memory: 148 MB
Memory available to Photoshop: 3250 MB
Memory used by Photoshop: 80 %
Image tile size: 128K
Image cache levels: 4
OpenGL Drawing: Enabled.
OpenGL Drawing Mode: Basic
OpenGL Allow Normal Mode: True.
OpenGL Allow Advanced Mode: True.
OpenGL Allow Old GPUs: Not Detected.
Video Card Vendor: NVIDIA Corporation
Video Card Renderer: GeForce GT 420M/PCIe/SSE2
Display: 1
Display Bounds:= top: 0, left: 0, bottom: 768, right: 1366
Video Card Number: 2
Video Card: Intel(R) HD Graphics
OpenCL Unavailable
Driver Version: 8.15.10.2189
Driver Date: 20100728000000.000000-000
Video Card Driver: igdumd64.dll,igd10umd64.dll,igdumdx32,igd10umd32
Video Mode: 1366 x 768 x 4294967296 colors
Video Card Caption: Intel(R) HD Graphics
Video Card Memory: 1024 MB
Video Rect Texture Size: 16384
Video Card Number: 1
Video Card: %NVIDIA_DEV.0DF1.01%
OpenCL Unavailable
Driver Version: 8.17.13.553
Driver Date: 20120802000000.000000-000
Video Card Driver: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Video Mode:
Video Card Caption: %NVIDIA_DEV.0DF1.01%
Video Card Memory: 1024 MB
Video Rect Texture Size: 16384
Serial number: 90970819015185381107
Application folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\
Temporary file path: C:\Users\VDS\AppData\Local\Temp\
Photoshop scratch has async I/O enabled
Scratch volume(s):
C:\, 111,7G, 14,6G free
Required Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Required\
Primary Plug-ins folder: C:\Program Files\Adobe\Adobe Photoshop CS6 (64 Bit)\Plug-ins\
Additional Plug-ins folder: not set
Installed components:
   A3DLIBS.dll   A3DLIB Dynamic Link Library   9.2.0.112
   ACE.dll   ACE 2012/01/18-15:07:40   66.492997   66.492997
   adbeape.dll   Adobe APE 2012/01/25-10:04:55   66.1025012   66.1025012
   AdobeLinguistic.dll   Adobe Linguisitc Library   6.0.0
   AdobeOwl.dll   Adobe Owl 2012/02/09-16:00:02   4.0.93   66.496052
   AdobePDFL.dll   PDFL 2011/12/12-16:12:37   66.419471   66.419471
   AdobePIP.dll   Adobe Product Improvement Program   6.0.0.1654
   AdobeXMP.dll   Adobe XMP Core 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPFiles.dll   Adobe XMP Files 2012/02/06-14:56:27   66.145661   66.145661
   AdobeXMPScript.dll   Adobe XMP Script 2012/02/06-14:56:27   66.145661   66.145661
   adobe_caps.dll   Adobe CAPS   6,0,29,0
   AGM.dll   AGM 2012/01/18-15:07:40   66.492997   66.492997
   ahclient.dll    AdobeHelp Dynamic Link Library   1,7,0,56
   aif_core.dll   AIF   3.0   62.490293
   aif_ocl.dll   AIF   3.0   62.490293
   aif_ogl.dll   AIF   3.0   62.490293
   amtlib.dll   AMTLib (64 Bit)   6.0.0.75 (BuildVersion: 6.0; BuildDate: Mon Jan 16 2012 18:00:00)   1.000000
   ARE.dll   ARE 2012/01/18-15:07:40   66.492997   66.492997
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2012/01/18-15:07:40   66.492997   66.492997
   BIBUtils.dll   BIBUtils 2012/01/18-15:07:40   66.492997   66.492997
   boost_date_time.dll   DVA Product   6.0.0
   boost_signals.dll   DVA Product   6.0.0
   boost_system.dll   DVA Product   6.0.0
   boost_threads.dll   DVA Product   6.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.0.5.19287   2.0.5.19287
   CoolType.dll   CoolType 2012/01/18-15:07:40   66.492997   66.492997
   data_flow.dll   AIF   3.0   62.490293
   dvaaudiodevice.dll   DVA Product   6.0.0
   dvacore.dll   DVA Product   6.0.0
   dvamarshal.dll   DVA Product   6.0.0
   dvamediatypes.dll   DVA Product   6.0.0
   dvaplayer.dll   DVA Product   6.0.0
   dvatransport.dll   DVA Product   6.0.0
   dvaunittesting.dll   DVA Product   6.0.0
   dynamiclink.dll   DVA Product   6.0.0
   ExtendScript.dll   ExtendScript 2011/12/14-15:08:46   66.490082   66.490082
   FileInfo.dll   Adobe XMP FileInfo 2012/01/17-15:11:19   66.145433   66.145433
   filter_graph.dll   AIF   3.0   62.490293
   hydra_filters.dll   AIF   3.0   62.490293
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   image_compiler.dll   AIF   3.0   62.490293
   image_flow.dll   AIF   3.0   62.490293
   image_runtime.dll   AIF   3.0   62.490293
   JP2KLib.dll   JP2KLib 2011/12/12-16:12:37   66.236923   66.236923
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   10.0
   LogSession.dll   LogSession   2.1.2.1640
   mediacoreif.dll   DVA Product   6.0.0
   MPS.dll   MPS 2012/02/03-10:33:13   66.495174   66.495174
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CS6   CS6
   Plugin.dll   Adobe Photoshop CS6   CS6
   PlugPlug.dll   Adobe(R) CSXS PlugPlug Standard Dll (64 bit)   3.0.0.383
   PSArt.dll   Adobe Photoshop CS6   CS6
   PSViews.dll   Adobe Photoshop CS6   CS6
   SCCore.dll   ScCore 2011/12/14-15:08:46   66.490082   66.490082
   ScriptUIFlex.dll   ScriptUIFlex 2011/12/14-15:08:46   66.490082   66.490082
   tbb.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   3, 0, 2010, 0406
   TfFontMgr.dll   FontMgr   9.3.0.113
   TfKernel.dll   Kernel   9.3.0.113
   TFKGEOM.dll   Kernel Geom   9.3.0.113
   TFUGEOM.dll   Adobe, UGeom©   9.3.0.113
   updaternotifications.dll   Adobe Updater Notifications Library   6.0.0.24 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   6.0.0.24
   WRServices.dll   WRServices Friday January 27 2012 13:22:12   Build 0.17112   0.17112
   wu3d.dll   U3D Writer   9.3.0.113
Required plug-ins:
   3D Studio 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Accented Edges 13.0
   Adaptive Wide Angle 13.0
   ADM 3.11x01
   Angled Strokes 13.0
   Average 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Bas Relief 13.0
   BMP 13.0
   Chalk & Charcoal 13.0
   Charcoal 13.0
   Chrome 13.0
   Cineon 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Clouds 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Collada 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Color Efex Pro 4 NO VERSION
   Color Efex Pro 4 NO VERSION
   Color Halftone 13.0
   Colored Pencil 13.0
   CompuServe GIF 13.0
   Conté Crayon 13.0
   Craquelure 13.0
   Crop and Straighten Photos 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Crop and Straighten Photos Filter 13.0
   Crosshatch 13.0
   Crystallize 13.0
   Cutout 13.0
   Dark Strokes 13.0
   De-Interlace 13.0
   Dicom 13.0
   Difference Clouds 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Diffuse Glow 13.0
   Displace 13.0
   Dry Brush 13.0
   Eazel Acquire 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Embed Watermark 4.0
   Entropy 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Extrude 13.0
   FastCore Routines 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Fibers 13.0
   Film Grain 13.0
   Filter Gallery 13.0
   Flash 3D 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Fresco 13.0
   Glass 13.0
   Glowing Edges 13.0
   Google Earth 4 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Grain 13.0
   Graphic Pen 13.0
   Halftone Pattern 13.0
   HDRMergeUI 13.0
   IFF Format 13.0
   Ink Outlines 13.0
   JPEG 2000 13.0
   Kurtosis 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Lens Blur 13.0
   Lens Correction 13.0
   Lens Flare 13.0
   Liquify 13.0
   Matlab Operation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Maximum 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mean 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Measurement Core 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Median 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mezzotint 13.0
   Minimum 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   MMXCore Routines 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Mosaic Tiles 13.0
   Multiprocessor Support 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Neon Glow 13.0
   Note Paper 13.0
   NTSC Colors 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Ocean Ripple 13.0
   Oil Paint 13.0
   OpenEXR 13.0
   Paint Daubs 13.0
   Palette Knife 13.0
   Patchwork 13.0
   Paths to Illustrator 13.0
   PCX 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Photocopy 13.0
   Photoshop 3D Engine 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Picture Package Filter 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Pinch 13.0
   Pixar 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Plaster 13.0
   Plastic Wrap 13.0
   PNG 13.0
   Pointillize 13.0
   Polar Coordinates 13.0
   Portable Bit Map 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Poster Edges 13.0
   Radial Blur 13.0
   Radiance 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Range 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Read Watermark 4.0
   Reticulation 13.0
   Ripple 13.0
   Rough Pastels 13.0
   Save for Web 13.0
   ScriptingSupport 13.0
   Shear 13.0
   Skewness 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Smart Blur 13.0
   Smudge Stick 13.0
   Solarize 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Spatter 13.0
   Spherize 13.0
   Sponge 13.0
   Sprayed Strokes 13.0
   Stained Glass 13.0
   Stamp 13.0
   Standard Deviation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Sumi-e 13.0
   Summation 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Targa 13.0
   Texturizer 13.0
   Tiles 13.0
   Torn Edges 13.0
   Twirl 13.0
   U3D 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Underpainting 13.0
   Vanishing Point 13.0
   Variance 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Variations 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Water Paper 13.0
   Watercolor 13.0
   Wave 13.0
   Wavefront|OBJ 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   WIA Support 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   Wind 13.0
   Wireless Bitmap 13.0 (13.0 20120315.r.428 2012/03/15:21:00:00)
   ZigZag 13.0
Optional and third party plug-ins:
   Camera Raw 7.1
   Nik Selective Tool 2.1.3.17256
Plug-ins that failed to load: NONE
Flash:
   Mini Bridge
   Kuler
Installed TWAIN devices: NONE

I was just being sarcastic. I knew it is a feature while searching for a way to fix the issue awhile back. I am very interested in knowing if any user out there could somehow fix the problem by reseting, reinstalling, etc. I got an update a few hours ago, and that didnt fix it either.
I have tried a lot of suggestions, and the only one seems to be working for me is to turn on "Scrubby Zoom"
Noel,
I run Adobe CS5 on MBP 10.6 and CS6 on MBPr 10.8. No additional plugins, English US keyboard. The laptops come with standard configuration... nonetheless, they both have the same issue.
I am sure my computers have different settings from others, but this issue does not seem to be isolate as there are other users have experience it too.
I personally, don't think it is too hard to re-create. Most likely happen when
1. Hold down space+command to zoom in
2. Release keys, then hold down space and start moving around
3. there you go, "bird's eye view" comes
One thing I notice is that the problem does not occur all the time.
-B

All photos suddenly look grainy UNTIL I zoom in [Photoshop CC]

A couple of days ago, all the sudden, every picture I bring up in Photoshop CC looks very grainy until I zoom in a couple of times. When I bring it up in Bridge, it looks fine, even after I edit it in PS. A few days ago I had been working on photos from the same photo session and they didn't do it. Now when I bring up one of those photos from several days ago they also look grainy, too - but only when I view them full size in Photoshop CC. When I zoom it, they look normal, but I can't edit them zoomed in. I restarted the computer but that didn't help.Do I need to change a setting in Photoshop? Hope this makes sense. Thanks for any help. ~Valerie

Hi, I am having exactly the same problem. Very frustrating as I have deadlines to meet. Graphics that I am placing into a PSD were designed by graphic designers, and have used them before, but suddenly they are very grainy. I have looked at the suggested solution but Performance is set at 4. I've attached a picture should like as well as what the PSD file looks as a screen shot. Hope that someone can help. Many thanks.

ACR 4.5 Did Not Fix Photoshop Bug Crashing

I posted this in June
Bug: Multiple Files Open ACR Crashes Photoshop...
Buko, "Bug: Multiple Files Open ACR Crashes Photoshop..." #1, 10 Jun 2008 2:57 pm
I just went back to my normal workflow with ACR 4.5 (after leaving it because of the problem) and got the new Photoshop crash report after working on about six files.
The workflow: .nef> Bridge> ACR> 16-bit aRGB (moving sliders Black/Mids/Exposure usually generates the crash)> resizing to 500 pixels and Save AS .psd (leaving the .psd files open seems to be the switch that causes the problem)
I can repeat the problem consistently:
Drag folder containing D200/D300 .nef files into Bridge, and going to work as described...if I don't leave my .psd files open I don't have a problem, if I leave them open as I work, I usually get the crash after 5-10 files.
I emailed crash reports to CC back in June,

UPDATE: I pulled the 12gb of macramdirect ram and tested with only 2gb OEM Apple ram (to rule out the 3rd-party ram per Jeff Schewe's theory I duplicated the crash within 15 minutes. My money remains on the BUG theory, but will swap out the OEM ram and continue...if that doesn't work I will install ACR 4.6 and retest... Today's CRASH REPORT: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd"> <crashreport version="1.1" crVersion="2.5.0.02272007" applicationName="Photoshop" applicationVersion="10.0.1" build="10.0.1 (10.0.1x20071012 [20071012.r.1644 2007/10/12:09:30:00 cutoff; r branch]), ©1990-2007 Adobe Systems Incorporated"> <time year="2008" month="10" day="2" hour="15" minute="50" second="29" /> <user guid="5F46434A-15D5-4A63-A652-31682CE59DD0" /> <system platform="macintosh" osversion="10.5.5" applicationlanguage="en" userlanguage="en" oslanguage="en_US" ram="2048MB" machine="i386" model="MacPro3,1" cpuCount="8" cpuFreq="2800MHz" busFreq="1600MHz" /> <crash exception="Unmapped Memory Exception" instruction="c683068b"> <backtrace crashedThread="0"> <thread index="0"> <stackStatement index="0" address="0xffff07c2" symbolname="unknown"/> <stackStatement index="1" address="0x9327efd9" symbolname="__ZN18CTextensionIOSuite17SearchIOSuiteTypeEmP11TDataHeaderh"/> <stackStatement index="2" address="0x9327ef17" symbolname="__ZN18CTextensionIOSuite16FreeSuiteObjectsEm"/> <stackStatement index="3" address="0x9327eee6" symbolname="__ZN18CTextensionIOSuite16FreeSuiteObjectsEv"/> <stackStatement index="4" address="0x9328c9af" symbolname="__ZN18CTextensionIOSuite4FreeEv"/> <stackStatement index="5" address="0x93248cd7" symbolname="__ZN22CTextensionEditCommand4FreeEv"/> <stackStatement index="6" address="0x9328c7ed" symbolname="__ZN15OpaqueTXNObject4FreeEv"/> <stackStatement index="7" address="0x9328c71e" symbolname="_TXNDeleteObject"/> <stackStatement index="8" address="0x2fcc4a6f" symbolname="_EntryFM"/> <stackStatement index="9" address="0x2fc9286e" symbolname="_EntryFM"/> <stackStatement index="10" address="0x2fc58104" symbolname="_EntryFM"/> <stackStatement index="11" address="0x2fc53c7e" symbolname="_EntryFM"/> <stackStatement index="12" address="0x2fc94c2e" symbolname="_EntryFM"/> <stackStatement index="13" address="0x2fc58104" symbolname="_EntryFM"/> <stackStatement index="14" address="0x2fc53c7e" symbolname="_EntryFM"/> <stackStatement index="15" address="0x2fc74047" symbolname="_EntryFM"/> <stackStatemen

Photoshop bug: Smart Objects overwriting other Smart Objects when edited and saved in Illustrator

Experiencing issues when working with a large number (over 200) vector smart objects brought into Photoshop CS4 from Illustrator.
Things seemed to be going along nicely; if I needed to edit a Smart Object, I could double-click it, it would open in Illustrator and then I could edit and save it. Return to Photoshop and the Smart Object is updated. Swell and dandy. The issue started happen when I hit a large quantity of either vector smart objects (remember, over 200) or the many layers and groups within Photoshop (must be over 500). When I would double-click, open, edit, and save the vector Smart Object, the Photoshop Smart Object I was working on would update AND another/several other Smart Objects would update as well. Which, of course, would ruin the artwork, as suddenly I was seeing several instances of the same object. If it hadn't have been for ForeverSave, I many not have recovered the work.
It's rather hard to isolate the issue to see what's causing the problem. Here are some of the possible causes:
Running Snow Leopard on Mac
Many, many Smart Objects in file, perhaps enough to ruin the naming convention and cause bugs when Photoshop referenced the temp file
Many, many Photoshop layers and groups
Illustrator vector files copy+pasted from several different files (affects the naming convention perhaps?)
Some groups/layers in Photoshop are duplicates
To help make it a little clearer, you should know:
Running the most updated software / OS (that is until CS5 comes out)
Smart Objects showed no error until I had actually opened, edited, and saved the referenced temp file (i.e. VectorSmartObject1.ai)
Files saved and worked on from Dropbox (network folder)
Not looking for much of an answer to this question; I just wanted to see if anyone else had come across this bug. Also, Adobe PLEASE look into this as you begin testing for the next update. I have the file(s) if you need to replicate the issue. My best guess is that the naming convention of Vector Smart Objects has an odd character limit so when Vector Smart Object 200.ai is saved, Vector Smart Object 2.ai gets overwritten.

Have you tested this with Photoshop CS5 and Illustrator CS5? (the current versions, that came out last month)
If you duplicated a smart object layer, both layers refer back to the same file content. So when you change the file, both layers would be updated. That is intentional and explained in your manual. If you didn't realize this, that could explain what you are seeing.
If you placed separate files, then they should not be updated at the same time, because they will refer to separate files.
Yes, Smart Objects only update when you save the file.
You would need over 4 billion smart objects in one document to get Photoshop confused about which one refers to which file. And since the layer limit is much less than 4 billion, I doubt that is the cause.
There is no naming convention involved. We don't limit the filenames (except to platform standards and to include a file type extension).

Photoshop bug: cs6 and cc: interface freeze, no reaction

hello,
we discovered a potential bug or issue in photoshop:
under daily working conditions, 8h per day, during the last months/year i can observe the following behavior:
suddenly, at any action, the photoshop interface (all palettes, windows, everything) freezes and doesnt react on any mouse or button command. can wait for minutes, nothing happens.
found workaround: switch to finder by clicking with mouse pointer into the finder desktop,
and switch back to photoshop > interface is back and reacts again, everythings fine.
condition of bug: very annoying but can live with it so far through my workaround
frequenzy: several times a day (up to 20 or 30 times per day)
- reproduceable on mac osx 10.7 + 10.8 + 10.9
- reproduceable with photoshop cs6 and cc
- reproduceable on 3 different macs at 2 different working places so far
- mac pro 2006, mac pro 2012, imac late 2013 with each mac 48GB RAM or at least 32GB RAM (imac)
- reproduceable with 8 bit and 16 bit files, .psd and .psb
any idea?
thanks

If I remember correctly, and that is not always the case, I think that is a bug in Apple OS. Currently the cursor just dissapears and you have to do what you say to get it back.

Can't open new file - Where do I file photoshop bugs?

"Could not complete your request because of a program error." popups up when I try and File -> Open. My only work around has been to close and re-open photoshop, constantly.
2012 Mac Air OS, 10.10.2, Photoshop 2014.2.2 (20141204.r.310 x64). This did not happen before I updated photoshop.
** Where does one file bugs or feedback for photoshop? or does Adobe not care? **
I can't find a better location. I saw someone else posted a similar discussion questions Dec 30th, so obviously this is not being fixed. I find not opening new files to be pretty major function regression. If I open like 10 files when I first open photoshop it's ok, but then when I forget I need one more file, I see this error, the programs only been open 15mins, I've barely done anything to trigger a program error! I have to close and reopen everything. Making a new file is possible.

If what you see were "a bug", everyone would see it. If it's unique to you, especially if you have not yet deleted and recreated your Photoshop preferences, you cannot call it "a bug".
That error message suggests there may something wrong with your Photoshop install or some other fault on your system,
Don't cry wolf prematurely, lest Adobe really stops paying attention to you.
To re-create the preferences files for Photoshop, start the application while holding down Ctrl+Alt+Shift (Windows) or Command+Option+Shift (Mac OS). Then, click Yes to the message, "Delete the Adobe Photoshop Settings file?"
Note: If this process doesn't work for you while you're using a wireless (Bluetooth) keyboard, attach a wired keyboard and retry.
Important: If you re-create the preferences by deleting the Adobe Photoshop CS6 Settings file, make sure that you only delete that file. If you delete the entire settings folder, you also delete any unsaved actions or presets.
Reinstalling Photoshop does not remove the preferences file. Before reinstalling Photoshop, re-create your preferences.
NEW Video! Julieanne Kost created a video that takes you through two ways of resetting your Photoshop preferences. The manual preference file removal method is between 0:00 - 5:05. The keyboard shortcut method is between 5:05 - 8:18. The video is located here.
Mac OS
Important: Apple made the user library folder hidden by default with the release of Mac OS X 10.7. If you require access to files in the hidden library folder to perform Adobe-related troubleshooting, see How to access hidden user library files.

Another Edit in Photoshop bug

When I highlight an image and select "Edit in Photoshop" the image opens in Photoshop just fine.
The problem arrises when I am finished editing and click "Save" in photoshop. The edited image does not appear in my Lightroom Library. Instead, I only see the original image. The really quirky thing is that the original now has bars on each side of it indicating a stack and the little white square appears at the top left displaying "1 of 2". If you hover over it with the mouse a pop-up says "This image is part of a stack" But if you double click it or choose "Expand stack" it still only shows the one image.
What gives? Both 2.0 & 2.1 have this issue. I never experienced this in 1.X so the bug is new.

Jao,
Nope. Everything is just as it was when I used LR 1.X together with CS3. I upgraded to LR 2.0 and CS4 about the same time so it could be an issue with either but I suspect it is in LR.
Here is another quirk I just discovered...
If I double click on the white square indicating the number of photos in the stack, both images (the PS edited & the original) show up in LRs compare view on my second monitor. The edited image still does not show in my Library screen even though it's on the second monitor in compare view. Strange.

Roundtrip editing with Photoshop - bug in iPhoto :-(

I've setup Photoshop as external editor. Opening the photo in Photoshop works fine. I save as .jpg. But iPhoto doesn't seem to recognize the changed photo. And continues to show the edited photo in it's original state. Actually showing it twice. But not with the edits.
Now I looked at the folders. iPhoto 11 has the folder Masters for the pictures, but the external editing pics go through the folder Previews. And hence saving ends up in Previews. Since Masters is a hidden folder; you can't even save the new jpg file there. Looks like a bug to me...
The external option - save as, and reimport is just a pain... that I can't recommend to anyone in my family. I personally use Lightroom + Photoshop for myself, and it works like a charm.

Sorry, but it is one of the above.
That's a setting in Photoshop. It's defaulting to psd for saving, so when you "flatten... so it can be saved as a JPG" you're doing a Save As.
See Old Toad's post here
https://discussions.apple.com/message/17390148#17390148
for details on how to set it up.
Regards
TD

Photoshop Bug: Sliders getting stuck to mouse after release (Mac OS)

When dragging various sliders in Photoshop CS5, very often these sliders get "stuck" and move with the mouse even though you have released the mouse. Say you are dragging a slider to set the brush opacity to 50%. When you have set it to 50%, you release the mouse and move it away from the slider, only to find that the opacity still increases or decreases as you move your mouse. You have to click again to fix this, but then of course you have to go back and do it again.
Below is a small illustration (I can't take a screenshot of my mouse) of an example of when this happens:
This happens to me around once every 5 times I use a slider, i.e. extremely often. As you can imagine, it's very annoying and frustrating.
I use a Wacom Bamboo Fun tablet, and I never use Photoshop without it so I cannot confirm whether this bug happens with a mouse or just the tablet.
It doesn't just happen like on the above illustration, but also with any slider such as those in Adjustment Layers and Filters.
The bug does not happen when using tools on the canvas (thankfully). So the Brush tool, and every other tool, works fine and never gets "stuck".
I have the latest version of Photoshop CS5.
This is a bug that has always been in CS5 since the first version, and it has not been in previous versions of Photoshop.
Does anyone else have this issue? Anyone else with a Tablet?
I know there are large amounts of similar, extremely annoying bugs in CS5, but this one is just driving me crazy.
Late 2008 15" MacBook Pro
OS X Snow Leopard 10.6.7 (but the problem has existed way before 10.6.7)
Photoshop CS5 version 12.0.2

Chris—I'm sincerely sorry that you were called at home on a holiday weekend about my post. Sincerely. I'm sorry. That shouldn't have happened, and I apologize for that.
I do ask that you also understand that I spent my entire weekend trouble-shooting this issue—which is now several months old—while waiting for an answer or at least a respectful and helpful response of some sort. Here we are with another week down the tubes and still have yet to receive some sort of expression of an Adobe employee taking my case seriously. I don't know if you—or anyone else—is investigating this. As best I can tell, you are not—and I base that on the series of confusing (and in some cases, patently false) assertions that you made regarding the facts of this matter—including confidently promoting the notion that this is not a problem with Photoshop CS5 (which it clearly is), and the notion that I hadn't done anything to narrow down the list of possible causes—which I clearly have. If you disagree, as you claim to, with either of those statements—then the very least you (or someone at Adobe) can do is to take ten minutes out of your schedule to draft a proper, logical and honest assesment of why you have come to those conclusions. I don't think that's asking too much at all. In fact, it's very disappointing that I've had to expend as much effort as I have to deal with this issue—and I still don't have an official, "right on, we're working on it," from you guys.
If you want to make a case that it was abusive of me to telling you that Layer Styles was likely the cause of this issue—go right ahead. I admit that my entire statement was a bit "hot," but you have yet to even acknowledge the validity of my concern—much less the tremendous effort I've undertaken at my own personal expense (and at your/Adobe's benefit) to contribute to the resolution of this problem... or the real-world dollars and opportunity cost to my creative reputation. Do you have many other users who go to these lengths when identifying bugs? I doubt it. As I've told you in another thread—if you've heard from me, it's only after I've already expended significant effort trying to solve the problem on my own. I don't whine about stuff and ask other people to fix it, if I can fix it myself. But I can't. I'm not a programmer, and I don't know how to run any diagnostics on my own—although trust me—I've tried. I've tried Xcode, and learning Applescript to see if I could craft my own workaround or identify the issue with even greater clarity. But I don't know either of those technologies, and it's not work that I should be doing anyway. There is a reason that a CS5 Design Master license costs upwards of $2,500, right? I've gotten much more attentive and respectful response from free apps than I've gotten from Adobe over this issue. What is that license for, if not for respectful customer service?
I have never received a paycheck from Adobe, Chris. I receive (small) paychecks when I get my work done—which I have not been able to do for over a week now... and this is not the first time that has happened as a result of this bug. And the week before this reappeared, I spent a significant amount of time testing out CS6 and taking notes to share with you and your development team—for no other reason that that I know this program inside and out (or at least large portions of it), and want to contribute to it in any way I can. So yeah... I was angry. Truthfully—I still am. My paycheck isn't even the reason I do what I do. I do what I do because it fulfills me on an emotional and spiritual level—which I stated in my very first post back in April. Suffice to say—I feel spiritually and emotionally drained right now. I'm just so incredibly exhausted, having spent the last couple hours nearly driven to tears by the combination of a fulll week of never-ending frustration, the loss of an important client and my favorite project, and what seems to be a total disregard for my case by you and whomever else from Adobe has read these posts without taking action to begin bringing about resolution.
Again—if you have a case to make, then make it. Thus far, you've said a few things which made it seem like either a) you haven't even read the top-line details of my detailed reports, or b) that you are determined to squash me—not the bug. I've explained why I've come to those conclusions very clearly. Your assertion that I hadn't narrowed anything down is so demonstrably false that I consider that to be an abusive statement. Your mention of Wacom drivers and third-party-related possibilities right after I'd spent about an hour composing a post (following up on a couple of days worth of volunteer trouble-shooting) detailing to the nth degree why it absolutely could not be either one of those things is totally perplexing, to the point where it make so little sense that someone of your presumed intelligence (i.e. a big-shot developer for one of the worlds most well-known applications) could actually respond that way after reading any part of what I'd just wrote. It makes no sense. Either you didn't read it, or you did read it, and you had a reason for making a statement that you knew wasn't in line with the facts of the matter. I don't know which one it is, but it's one of those things, unless I'm totally missing something.
You have offered a few terse responses to my very detailed reports—and in the few short sentences that you've wrote, you've made many statements that have no effect on pushing the issue forward or getting it closer to resolution. I don't want it to be a personal issue—but I don't feel like I made it personal until you did. Yes, my statments were direct and pointed—but at least they've been transparent, articulate and well-explained. You continue to speak about things like my continued accusations, your weekend, the TOS of the forum, and all sort of things that only exacerbate an already-painful, already-costly issue. I've told you that I am determined to get resolution on this issue—and I am serious. I will not accept blanket dismissals, and I will not be intimidated into backing down from my demand for a resolution. I have helped you get as far as I can get on my own, and I am willing to continue to help in any way I can.
I quit a very high-paying job 4 years ago to pursue a career as a designer. I make next to nothing now, but I feel fullfilled because of the creative process. This bug has prevented me from all fulfillment. It has strained my personal and professional relationships, and has taken a heavy emotional toll on me. Please step up and make an effort to get it resolved—or at least assign someone else to solve it. I can provide whatever you need from my end—and again, I'm sorry for your phone call this weekend.
-Jason

Creative Cloud Photoshop Bug

I'm not interested in troubleshooting with anyone, but just wanted to know if anyone knows if Adobe has fixed their bugs with Creative Cloud photoshop, mine is not working and is very frustrating to know that other people have the same problems, will this software work ? yes or no? In case anyone is interested I get a blank screen every time I open a document, so it's useless, and when I resize the Photoshop window it can not do a good job of resetting the included tools.

"There are however situations when that safety mechanism fails and the features are enabled despite the configuration not supporting it. This can lead to crashes or show strange artifacts like a black document window, strange strip or triangle patterns in the main window or images only displaying partially"
Funny how I just fixed it by changing a setting within Photoshop to disable/enable the hardware acceleration, took me 2 minutes to google search the problem related with the blank image. However I updated my video driver and the problem never came back, so I guess my computer does not support Photoshop extended features.

Lightroom to photoshop bug

Hi, the "edit in photoshop" from lightroom function is not workin. ps cc 2014 is starting but not opening the foto. i tried everything several times: deinstalling / installing with removing the prefs. repaired all user privileges. it's so frustrating. one month ago, revel was down for almost 4 weeks because of the ios bug. and now this. what's going on at adobe? any help appreciated. best regards, Arne

Hi,
Adding to ssprengel's correct answer:
Getting the update:
Look for the update in the Creative Cloud application and click “Update”. If it doesn’t appear, you may need to quit and re-launch the Creative Cloud application.
If you don’t have the Creative Cloud application running, start Photoshop and choose Help > Updates.
The Adobe Application Manager will launch. Select Adobe Photoshop CC (2014) and choose Update.
Confirming the update worked:
In Photoshop, choose Help > About Photoshop (Win), or Photoshop > About Photoshop (Mac)
The version at the top should say 2014.1.0 Release
For background, Ps 2014.0 introduced a bug that caused some cross application communication to breakdown. We have fixed this in the 2014.1 (aka 15.1) release just recently published.
Sorry for the trouble.
regards,
steve

Zooming like Photoshop

Why not have one zoom tool like Photoshop. You can drag the Zoom(Z) tool over ANY area of an image and it will zoom to that point and then a full zoom out would be the shortcut Ctrl>0 Only 2 clicks. I could do anything in milliseconds with that capability. I bet you could do this when you're fixing the Spectral view in a Photoshop file.
With one zoom tool it would totally do away with the whole zoom box but leave it in the window menu in case somebody yaps 'cos it's missing :D
BTW, don't forget to include it in Edit view as well.
Mark

I more or less do that now with a keyboard short cut to View Zoom to Selection. Then I just select the bit I want to zoom to by dragging the left clicked mouse over it and then use the shortcut key. The already assigned "\" key zooms back out fully horizontally.

Dreamweaver/Photoshop Bug?

My System:
- Dreamweaver 8
- Photoshop CS
- iMac Intel Core Duo (OS X 10.4.8)
My Problem:
- I would like to edit the html in one or more of the
existing template files used by Photoshop CS's automated "Web Photo
Gallery" plugin. I have done this for two years with much success
on my old Windows PC system. When using the PC I would:
1) locate an existing template file (like "IndexPage.htm");
2) edit the html in FrontPage;
3) save the new file(s) to a new template folder; and
4) run the automated Web Photo Gallery plugin in Photoshop.
As I said, I've never had a problem -- until now.
- Now that I have migrated to an iMac, I am using a newer
version of Photoshop (CS) and instead of FrontPage, I now use
Dreamweaver 8. But get a load of this -- if I so much as "OPEN" one
of the existing template files that came with Photoshop CS using
Dreamweaver 8, and then "SAVE AS" over the existing file (no edits,
just an OPEN and SAVE), Photoshop's automated Web Photo Gallery
plugin creates web pages with "missing" html. I kid you not.
- Below is a sample of what the code in a "good" index.htm
file looks like vs. the code in a "bad" index.htm file. Remember,
the only difference between the template files used by Photoshop CS
when creating these web photo galleries is that the "good" template
is the original file from the installation CD, and the "bad"
template was that same file OPENED and SAVED using DW 8.
Good index.htm code:
<BODY bgcolor=#FFFFFF text=#3366FF link=#0000FF
vlink=#800080 alink=#FF0000>
<TABLE border="0" cellpadding="5" cellspacing="2"
width="100%" bgcolor=#F0F0F0>
<TR>
<TD>New York Harbor,
NYC: Working Harbor Day 2006, Part 2
 
 1/27/07
 
 <A href="mailto:"></A>

</TD>
</TR>
</TABLE>
<CENTER>
<TABLE border="0" cellpadding="0" cellspacing="2"
width="200">
<TR>
</TR>
</TABLE>
</CENTER>
<CENTER><TABLE cellspacing=10 cellpadding=0
border=0>
<TR>
<TD align="center"> <A name=1
href="pages/01_192Books.htm"><IMG
src="thumbnails/01_192Books.jpg" height="56" width="75" border=0
alt="01_192Books"></A> </TD>
Bad index.htm code:
<BODY bgcolor=#FFFFFF text=#3366FF link=#0000FF
vlink=#800080 alink=#FF0000>
<TABLE border="0" cellpadding="5" cellspacing="2"
width="100%" bgcolor=#F0F0F0>
<TR>
<TD>New York Harbor,
NYC: Working Harbor Day 2006, Part 2
 
 1/27/07
 

<TD align="center"> <A name=1
href="pages/01_192Books.htm"><IMG
src="thumbnails/01_192Books.jpg" height="56" width="75" border=0
alt="01_192Books"></A> </TD>
Any ideas as to what is causing this error? I've tried a
number of things to help me isolate the issue. I assume that this
problem has something to do with the way that DW 8 saves html
files, or perhaps it has something to do with the way Photoshop CS
reads html files. The thing is that the two template files are
IDENTICAL when you compare their code -- what gives?
Thanks in advance.

DWD,
Thanks for taking the time to read and respond to my post.
Based on your response, I think that you -- and perhaps others --
might be unclear as to the nature of my issue with Photoshop CS1
and DW 8, so I'll quickly reivew it again.
1. Photoshop CS 1 includes an "Automate" plugin called "Web
Photo Gallery."
2. This plugin includes several "templates" which generate
various web ready photo gallery formats when selected.
3. These "templates" are in fact a collection of html files
-- grouped together by template -- which Photoshop uses when
creating web ready photo galleries (once you've run the automated
plugin.)
4. These "template" files may be editted -- Photoshop's own
user manual confirms this fact -- and I have done so in the past
with much success. This gives me much more control over the final
web gallery files created by Photoshop (i.e. size & resolution
of images & thumbnails, gallery layout, CSS formats, etc.) than
is achievable by using the DW 8 web gallery function you mentioned.
5. I have never had an issue creating web photo galleries in
Photoshop using template files that I have "customized." Just to be
clear -- I customize the template file BEFORE I run the plugin, so
this is not an issue of my not being able to edit html files
GENERATED by Photoshop's plugin (I think.) Instead, it's an issue
of Photoshop creating web photo gallery files that are missing
random bits of code whenever I run the plugin using a template that
I have customized.
6. But here's the thing -- if I so much as OPEN a template
file in DW 8 and then SAVE AS over the original file, Photoshop
will create web photo gallery pages missing random bits of code,
even though this "editted" template file has EXACLY THE SAME CODE
as the original template file. When I revert back to using the
original template files, Photoshop generates web photo gallery
files with all of the code intact - no problems at all. What is the
deal?
7. I have only encountered this issue using Photoshop CS1 and
DW8 on my new iMac. I have never had this issue when using
Photoshop 7.0 and FrontPage 2000 on my Windows PC to achieve the
same end.
Is there some "invisible" code that DW8 inserts every time
you open and save a file? I cannot SEE a difference between the
code, file name and file extension of the original template file
and the one I opened/saved in DW8, so why on earth would I get two
different file results when running the "same" template through the
same plugin? (See the "good" and "bad" code example in my original
post.)
Help!!!!!

Zooming in photoshop bug

Similar Messages

Maybe you are looking for