Bug Reports

I've Noticed this weird behavior after the latest 21.1.0 update:When panning, the canvas  basically refreshes only after I have stopped my panning motion, so that there's no smooth movement during panning, only the state before panning and the state after panning. Feels extremely choppy. Only if I scroll REALLY slowly - like snail speed - I see the canvas following along my motion. As soon as I accelerate to a normal panning speed, the above behavior goes into effect.I first thought that this might be a graphics card driver issue but then I noticed that when I turn on "flick panning" in the preferences, suddenly panning is performed smoothly (but, as to be expected, with the annoying floaty overshooting motion of flick panning, that I'd like to avoid).If someone can confirm, this might be an issue worth investigating.   UPDATE 20th April 2021:   At least two users confirmed that the Navigator window plays a role in this problem. Scaling the Navigator window or closing it

Please download this action. And run it.https://yadi.sk/d/IFn5lyAW9Z5BiwIt will create a file. Will make 9 layerComps in it and offer to save. Save it.Note that the layerComps in file goes in order.Close the file and open the saved one.It will have some duplicated layerComps. I often duplicate 2 and 2. This is because Photoshop created them with the same ID. If you quickly create layerComps, then they can create the same ID and everything will be messed up.A bug appears even in CC2018.There is no bug in CS6.Please confirm.

I export JPEG images from retouched RAW files, using Save for Web. Metadata is set to "All Except Camera Info." Before retouching, I add extensive metadata to the RAW files, including text to the dc:description field. Unfortunately, that one field is stripped out during SFW export. As far as I can tell, no other metadata is stripped from dc namespace. Please do not tell me to use Export or Save As. Any such answer is off-topic and not helpful. I just want to report this bug (assuming it won't be fixed, though.) Photoshop 22.5.1, Windows 10 Pro.

I've just downloaded the new photoshop update (22.01) and I noticed there is no classic red area when you change Brush size and feathering (when using keyboard shortcut OPTION+CONTROL).    it is quite frustrating

I recently bought an HP Spectre X360 14 with an i7-1195G7 (and 16GB RAM & 1TB SSD with Optane cache) running Windows 11 Pro (21H2, build 22000.438.)   Photoshop (v.23.1.1) crashes when doing something as basic as applying a Smart Sharpen filter unless I disable Graphics Acceleration, specifically using OpenCL, within Photoshop. I'd like to be able to experience the benefits of Graphics Acceleration in Photoshop.   Yesterday I updated the Intel graphics driver on my device from v 27.20.100.8664 (dated 6/1/2021) to v 30.0.101.1191 (dated 12.3.2921) and Photoshop was auto-updated three days ago, but the problem persists.   I don't see any other reports of such problems, but would like to know if there is any way to resolve this. I live in Mexico and had flown to New York City just to buy this computer, and I'm considering flying back to NYC to return it. Do I have a defective computer, or can this be fixed?

Photoshop seems to work fine when I use my finger on the pen display, but when I touch the actual pen to the screen it immediately freezes and crashes a few minutes later. I've tried restarting the pen display, the computer, photoshop, I tried changing scratch disks and back again, I've updated everything except my iOS, which I'm afraid to update until all those bugs are fixed.

New CMYK document (A4/300dpi)  One layer added. Shape tool => Add Rectangle => fill color => color picker      

When I save an image coming from the RICOH Theta Z1 as TIF in Photoshop the makersnote metadata is not saved. There's also no difference to saving with no compression or LZW.   I can't imagine that I am the only one with this issue... And I really think Photoshop should pass on ALL metadata, period!   This is the original image maker (aka makernotes) metadata: And here's what's left (nothing) when the TIF is saved in Photshop: I hope there's going to be a fix for this some day because for now I need to copy the metadata over using commandline and ExifTools...

Since upgrading Photoshop to 22.5.0 on my Mac OS 11.5.2 I have a problem with the following command in all my AppleScripts that feature it:   make new path item with properties {entire path:PathDetails, name:"Path Name", kind:normal}   Photoshop will throw the error "Could not complete the command because of a program error.", but will continue on and execute the above command anyway.   I have wound back Photoshop to the previous version and the expected behaviour is restored.

PS 23.0.1 When editing an existing curves layer...  Make any change to the curve and then Command Z to undo.  The undo works and the history panel shows a step back.  All good.  Now Shift Command Z to redo.  The history panel shows the step forward but the curve remains in its current state.  The undo state.  There is now no way to redo the change.  If the first undo is done using the history panel, not Command Z, everything works as expected.  It's only the key command that breaks it.   iMac (Retina 5K, 27-inch, 2017) 4.2 GHz Quad-Core Intel Core i7 Big Sur 11.6.1

Hi Community,   We are using latest version of Photoshop (23.1.0). When using the color picker tool with Ruler tunred on on a full screen mode, the photoshop window showing glitches. This is happening only when the ruler is turned on. Otherwise it seems fine.   A sample image of the issue attached.

I am working with the latest Mac OS Big Sur 11.1 and with the latest Photoshop update, Photoshop 22.1.1 When I want to fill in the File Info my cursos disappeared. When I change the color of the interface to dark gray, the cursor in File Info returns. The same in Bridge. Command I gives me the File Info screen, as in Photoshop, but no cursor. And when I change the interface color to Dark Gray the cursor returns.  Until now this bug isn't fixed. When will this happen??  

Version: Photoshop CS6 and 2022 Platform OS: 64 bit, Windows 10 Pro Expected Result:  Image Processor save the various files to disk   Desired Workflow: 1. Open a image from a flatbed scanner consisting of many old photos. 2.  File -> Automate -> Crop and Straighten   This creates many tabs with one photo in each. 3. File -> Scripts -> Image Processor     select to "Use Open Images", select a folder for the processed images, select the filetype as TIF (any will work) 4.  Click Run   Photoshop errors instead of saving the various tabs into files.   First with a Script Alert that  "There were no source files that could be opened by Photoshop"   Then a second Script Alert: "Sorry could not process the following files"  followed by a list of a bogus directory name and the tabs names."You can reproduce the issue using the class-cars file below.

Take an Adobe RGB JPG, convert it to Lab, then save as a JPF or PDF (probably any format).  You'll note this metadata:   xmp:xmp-photoshop:colormode:Labxmp:xmp-photoshop:iccprofilename:Adobe RGB (1998)   No bueno.  My guess is that the field is just not being blanked or populated upon conversion to Lab.   Sending love and best wishes to all readers!  Peace. 

I've been having an issue in Photoshop, Bridge, and Illustrator for years and have finally found the solution to a bug that has been plaguing me across different version of Creative Cloud, different computers, and even different operation systems.   I have found that the Bevel & Emboss effect in Photoshop corrupts some of my files when viewed in Bridge. In the above illustration, the image on the left has a Bevel & Emboss effect and the image on the right is how the image should look . When I save the file and view it in Bridge I see the weird lines across the image. When I place the image into Illustrator the corruption is present. If I save a JPG the corruption is present. When I open the file in Photoshop the corruption is not present, and if I turn off the Bevel & Emboss the corruption is no longer visible in any of the ways I listed above.  As you can imagine, this has been very frustrating and annoying.   After really playing with it and taking a d

Lorsque j'ouvre un fichier Raw catalogué dans LR (Cloud) depuis l'interface initial de PS 2020, il s’ouvre correctement dans CameraRaw, mais même si je demande ensuite de Ouvrir l'objet, aucun calque objet dynamique n'est ouvert dans PS 2020.Regardez la vidéo, déolé, PS est en français.Remarque importante, si j'ouvre le même fichier depuis le finder, Je clic sur Ouvrir l'objet, j'ai correctement un calque d'objet dynamique contenant le fichier raw dans PS !Je pense qu'il s'agit d'un bug.Regardez la vidéo jointe.  

A crash happens consistantly when using Pattern Preview, steps to reproduce:- Create a document - Create a Solid color with a mask - Turn on View -> Pattern preview - Create a selection for part of the mask using any selection tool - Move that selection Using Move Tool - Crash occurs

When using multiple artboards in the one psd, when i try to use 'export as' to quickly export jpgs i'll be lucky if it exports two of the artboards. The menu closes as if its completed what you have asked it to do but it doesnt do anything.

When I am exporting an image using the Export As dialog, and I enter 200px for the width, it will sometimes automatically change to something else when I tab out (e.g. 196 or 197). My guess is that this has something to do with Photoshop translating my pixel input into a percentage with a limited number of decimal positions, but this is ridiculous. I need to be able to export my image to exact pixel dimensions and Photoshop should be able to do that.

It looks like there is a colour management bug in Export As. To test my working colour space is Adobe RGB, but I created a document in ProPhotoRGB and followed the process below:   a. I created a 16 bit document with a gradient running from RGB 07,53,25 to 50,98,50 in ProPhoto. (Readings are in 8 bit but document is 16 bit)   b. First I changed that to 8 bits - No visual change, Info from eydropper still shows gradient running from RGB 07,53,25 to 50,98,50 so no change in values either. That is as expected.   c. I stepped back in history to the 16 bit document   d. I used Export As to export a PNG in PNG24 format with no change of profile and the profile embedded. On reopening it opened in Prophoto but the values had changed as had the visual appearance. The gradient now ran from 0,77,33 to 53, 125, 60. Expected behaviour would be no change in teh colour values or visual appearance.   e. I repeated step "d" but used Save For Web (Legacy) again exporting P

I am finding that when i use "quick export as png" or "save for web" the layer effects are not applied...?   only when using "save a copy as" the layer effects are applied

In Photoshop 23.x (2022) for Windows, when adding a Hue/Saturation adjustment layer and a particular hue is targeted with the hand tool, moving the Hue slider does NOT cause the bottom-most gradient to reflect the different, modified choice of Hue. (i.e., the upper gradient reflects the hand tool's choice; the bottom, the newly chosen value.) Photoshop version 23.1.0 - no change in bottom gradient   This is DIFFERENT behavior from version 22.5.x and previous versions. I'm posting this again because an Adobe employee did not seem to understand what I was describing in a previoud post.   Photoshop version 22.5.1 - modified gradient, as expected

In Photoshop 23.0.2 under macOS Big Sur, when the artboard is not visible (i.e., when the window borders are flush against the edges of the artwork) and the entire image is visible on screen (i.e., no scroll bars), and you Select All, the marching ants are not visible like they should be. Sometimes, depending on the window dimensions, a sliver of the marching ants is visible on one or two edges, but most of the time, they are completely hidden. Here is a video of the problem:   

Photoshop 23.0.0 does not show active selection when stop popup is shown when running an action. If you cancel selection is visible again. Same action in 22 or 21 versions does show active selections on same system. Osx 10.15.7

Hello, it seems that there is a big bug with the "Slice Select Tool", especially with the "Divide" option.I have a 1792 x 512px image containing 64 x 64px tiles that I want to cut out. When I use the "Divide Slice" and split 64x64 pieces horizontally and vertically with the Preview option enabled. The preview is distorted (specially if the values of are greater in pixels per slice fields at default) and persistent, even when cancelling/closing "Divide" dialog and closing the current document.The "Divide Slice" option only works if the "Preview" option is not activated.   Regards, Nico.