CJButler
Adobe Employee
CJButler
Adobe Employee
Activity
Jun 11, 2025
Just to be transparent, there are currently two bugs open in this area:
Moving / Translating an Artboard hangs - This typically happens with Canvas Auto-Size enabled, since that feature moves and translates Artboards pretty much continuously on the virtual invisible canvas as things get moved around. The hang was introduced as a side effect of a bug fix for gradients: code which translates Artboards was switched to using a computationally very expensive algorithm. The defect was not detected because it only manifested with large documents with many Layers. The documents do NOT have to have gradients in them to be impacted - just the fact the expensive algorithm was being used is sufficient.
Gradients shift and change size when interacting with Artboard documents - This is an architectural issue that was identified earlier this year, and it is currently being worked on. Gradients were using the document bounds for content generation and placement. Given that Artboard documents have constantly changing document bounds, this causes unstable gradient calculation.
These two issues are tied together at this time. They are being actively worked.
Short-term, item (1) can be mitigated by disabling canvas auto-size, as previously suggested, or by setting the following line in PSUserConfig.txt: "TransformArtboardGradientFill 0"
This will cause other, older bugs with Artboards and Gradients to manifest, but if gradients are not being used, this might resolve the hang problems and be a viable short-term solution. I recommend using either one or the other of these approaches, but not both.
... View more
‎Jun 05, 2025
04:36 PM
We think we found the problematic code. The fix affects Windows only and has been made in the 26.8 release branch a few minutes ago.
... View more
‎Jun 04, 2025
07:45 AM
@donbarrum We've finally had someone reproduce in-house late last night, which is a huge leap forward in diagnosing the issue. We still don't know the cause, but we're able to actively hunt the bug now. We do know that the other fix put in last Friday which I had speculated might resolve the issue - does not. It's something else.
(In your OP, you indicated it happened in 26.0 and 26.1. Did it go away for 26.5 and then reappear in 26.6 and later?)
... View more
‎Jun 03, 2025
02:24 PM
@DonBar @Stephen - HU3D
Thanks - that's interesting information.
Just to confirm, the bad behavior happens without ANY keyboard events. Just selecting tools and using the mouse? No keyboard chording with the mouse? Any only while the mouse-button is still down during the drag? Or when the mouse-button comes up?
(edit add: And just to confirm, none of this is intentional behavior. It sounds like a pretty horrific user experience. I just wish we could see it happen under a debugger and figure out the conditions that allow it to happen.)
... View more
‎Jun 03, 2025
12:12 PM
@donbarrum
Yes please, if you wouldn't mind. Try each of the suggestions one at a time. That would be helpful data. I have a theory that might be in play: As you hit the space bar, and then drag with your mouse-down, is the space bar going up and down during the drag? Or is it just staying down? What I think is happening is that some other user interface element (I don't know which one - it is probably not be the other document window) is getting told to update itself, and it does a WM_ACTIVATE right in the middle of the drag. At that moment, the space bar is still down, so we get a WM_KEY event that gets redirected to the other (unknown) Window, which then decides to activate the Document Window that is in the background. I know a bug in this area was fixed this Friday, May 30, in our code base that will be released in 26.8, but I don't know if that fix affects the problem you are observing.
In general, if the update code for the unknown window decides that it doesn't need to do the WM_ACTIVATE, then the bug does not reproduce, which is why it is not seen by everyone. Furthermore, this behavior is all Windows only. Mac OS users would not be affected. /EndTheory
That "Modern UI" switch helps localize the code that possible caused the issue. Eventually this will be the new code as we retrofit Photoshop to be more modern. But that's a long-term task, and will likely take over a year. It's akin to changing parts on a car while everyone is still driving it. I won't comment on the strategy, as that decision has been made.
... View more
‎Jun 03, 2025
10:16 AM
@donbarrum
We're still trying to reproduce. A couple of things to try that may help narrow things down:
Try turning OFF Edit > Preferences > Technology Previews... > Enable Modern User Interface
Try turning OFF Window > Contextual Task Bar
What happens when you don't use Floating Windows, but instead use Docked Windows in the Application Frame. In that case, the foreground window should cover the entire canvas space. Do you still get unexpected switching to a different (background) window?
And some questions:
Is Edit > Preferences > Tools > Overscroll ON or OFF?
Do you normally run with Move Tool > Auto-Select = OFF, and then use the space bar (a keyboard event) to switch to the Hand Tool? Is that your normal workflow? What happens if you switch to the Hand Tool directly, without using the space bar to switch from the Move Tool to the Hand Tool?
... View more
‎Jun 02, 2025
06:06 PM
Nothing is ruled out at this point, although I do have and use a Wacom Cintique on one of my Windows System. That was the first one I tried. It is also a dual monitor setup. I watched the videos and tried for a bit, but could not reproduce. We'll keep looking and see if we can find someone internally who has an environment that can reproduce. Right now, it's a mystery.
... View more
‎Jun 02, 2025
01:21 PM
We're looking at it now. I've tried with a couple of versions of PS but cannot reproduce. I've asked another engineer to help, but so far we cannot, so I expect there's some secret sauce we're missing. The bug is still open and I agree it's annoying. We'll keep trying.
... View more
‎Jun 01, 2025
10:58 AM
2 Upvotes
Hi all,
Photoshop Beta 26.8.0 20250528.m.3090 was posted on Friday, May 30, with what I hope is a fix for this annoying bug.
The change affects Windows only. Not everyone is affected. Furthermore, as stated earlier, we've not been able to recreate the problem on Mac OS.
I have about 48 hours before 26.8.0 will be frozen and I won't be allowed to make further changes to that release. So if there are any issues regarding the fix for this bug in the Beta build, it would be helpful to hear about them as soon as possible. Thank you for any time you can spare to try the fix.
... View more
‎May 28, 2025
02:01 PM
MJChaudhary - Your assumptions are incorrect.
defaultgz1qlshjs8mz - you are correct.
As I write this, the current Beta is this: Adobe Photoshop Version: 26.8.0 20250527.m.3089
You should be looking for m.3090 or later.
I don't have control over when Beta releases get posted, but I think the next one will be this Friday, May 30.
... View more
‎May 27, 2025
01:52 PM
>>> Where do we find this build? I can see 26.8.0, but not sure how to find the datecode. Thank you.
Help > System Info: First line in that report.
Note that the build with the code change will not get built internally until tomorrow, and it will not be posted as a Beta release until some time later this week.
... View more
‎May 27, 2025
01:04 PM
1 Upvote
We have not been able to reproduce this issue on Mac OS. Are you using just a Mouse? Or is a Pen/Touch device involved? Does it reproduce reliably for you on PS 26.7? Any non-standard plugins? Are Contextual Task Bars enabled for you? We'll need to reproduce the issue on Mac OS in order to make progress. So anything that can aid duplicating your environment would be helpful.
... View more
‎May 27, 2025
12:47 PM
I've made some changes to try and improve this very annoying problem. As far as we can tell, this bug only affects Windows users. If there are any Mac OS Users who are experiencing this problem, we would like to know and we will need to open a new and different bug for investigation. Please try Adobe Photoshop (Beta) Version: 26.8.0 20250528.m.3090 or later. Please note the date code "20250528". As I write this, a build with a date code later than this, and build number higher than "m.3090" should be available in the Beta Release of Photoshop some time later this week. When it appears, please give it a try.
... View more
‎Feb 14, 2025
04:18 PM
Hi A.L.
Be advised that this patch is experimental and may have side effects. What the flag does is terminate the drag by reading the mouse-hardware directly, looking for button-up. Events which have not been processed yet would get processed later, after the hardware-driven button-up has been seen and handled, and might cause unexpected side effects, especially when working quickly. I'm just not sure how such side-effects might manifest in the user experience, and I'm much less confident of Pen-driven events with this flag enabled. It might be just fine for your purposes, but please be on the lookout for odd behavior. Thanks.
... View more
‎Feb 11, 2025
12:42 PM
1 Upvote
Hi A.L.,
Unfortunately I did not see the prior report dated October 11, 2024.
I've logged bug PS-151750 to track this issue specifically with the Transform Handle Mouse-Up not being detected. We'll accumulate information in that bug and see if we can reproduce.
Edit add: And thanks for the video!
... View more
‎Aug 26, 2024
10:34 AM
@DiodorS So we have this issue Open in our bug backlog. This weekend, I took a look at what it would take to sort it out. Unfortunately a blanket change to GetKeyState is not a safe thing to do. There are about 50 instances of direct calls to GetKeyState and GetAsyncKeyState, about evenly mixed, and from a casual survey of those calls, it's clear the original authurs had reasons for using deliberately one function or the other. Furthermore, there are ~ 6 additional code paths that abstract GetKeyState or GetAsyncKeyState into generic functions which are then abstracted into various utility function that are used all over the code base. So the implications of making such a change are unknown and risky. Things like using the ecsape key to cancel gestures may stop working, for example. I then looked into seeing if I could spot the specific code that trapped the ctrl key while the laggy brush waas painting, and while I can see the WM_KEYDOWN event, I cannot see which functions are calling GetAsyncKeyState while the paint stroke is being generated without adding a bunch of debugging code.
I have to get back to my assigned tasks, so I'll have to put this issue on hold for a while. The bug will go back into out backlog with some notes. I had hoped it would be easy to do, but it is not looking that way. I'll update this thread when I find some more time.
... View more
‎Jul 25, 2024
01:42 PM
Thanks - I'll add your comments to the bug and they will be seen and discussed during the review.
I think if we took your approach concept, we'd do it at the source level. I understand it well enough. The unintended ripple effects are hard to foresee when we consider all the workflows of our larger user base, so whatever we do, we will proceed with great caution.
... View more
‎Jul 25, 2024
09:57 AM
Good job - and interesting. I've added your comments and findings to the bug report. The bug will be will be reviewed next Wednesday.
As you might guess, the Photoshop Event Handling implementation is ... complex. Probably more than you can imagine. It has layers and layers of implementations applied and patched over the years. It requires support for multiple platforms (Mac, Windows, etc.). It has an unfortunate mix of an Event Queue pump, Paint Brush Stroke smoothing, real time hardware polling (we've worked hard to minimize this, but it is still required in places), Event Queue Peeking, and more. We've talked about rewriting the whole system, but our assessment is that it will be an extraordinary effort, and it will likely have a whole new set of bugs that will take years to find and fix.
One of the more useful bits of input you can provide between now and next Wednesday is your honest assessment of how this negatively impacts your day-to-day workflow, and whether your workarounds are tolerable or not.
I'll add your comments to the bug. Thanks again!
... View more
‎Jul 24, 2024
03:49 PM
Good info and Steps to Reproduce. Thanks. Logged a bug, PS-137040.
But I have to be honest, it's probably not going to get ranked very high by the Product Managers unless a lot of people complain, despite the impact on your workflows. It's probably been this way for several major releases. A Smaller Brush will reduce the lag, as might changing the Memory Tile sizes (not sure). It also depends on the Brush Tip Style; some complex brushes are lag machines when they are made big. It will take a major overhaul to change that behavior.
One thing that might be done is to somehow reject KB modifiers while a brush stroke is still painting. That code a very fussy, so we'd have to be very careful how we did that. We'd almost certainly upset someone else by changing that behavior without a great deal of care. So: High cost, which is also considered when evaluating what to fix.
... View more
‎Jul 07, 2024
01:56 PM
@Coreylehmanenterprises I am unaware of any such tools and this is not my area of expertise. This thread needs a CAI expert to chime in. Maybe some other User knows the answer to your question.
... View more
‎Jul 05, 2024
10:26 AM
At this point, we cannot reproduce without more information. Reproducing is critical for us to resolve the issue. I've logged an internal ticket to track all infomation, There was a fix for a freeze when using Flick Panning with the Hand Tool that went into 25.9. The fix was designed to prevent unsafe numerical values from being used. It's possible we missed a code path when making this fix; we'll certainly review the change. If you roll back to 25.8 AND disable Flick Panning, does the problem go away.? We'd like to collect an Event Log per these instructions: https://helpx.adobe.com/photoshop/kb/photoshop-event-logger.html
An Adobe Support Representative will reach out to you directly to collect the resulting log files.
... View more
‎May 13, 2024
10:18 AM
Thanks. Forwarded to trhe CAI team to see if that helps them reproduce. Hopefully one of them will chime in on this thread.
... View more
‎May 13, 2024
08:42 AM
I'm trying to get someone on the team engaged. They cannont reproduce. I presume you are on Windows (10? 11?) and Photoshop 25.7. Can you share a screen shot of your Preferences > History and Content Credentials Screen? I will make sure they see that.
... View more
‎May 12, 2024
10:28 AM
Is this unexpected behavior blocking any workflows? That will elevate the priority.
I did find these threads. Did you see them? (Never mind - I see you did)
(deleted links)
Cory is the one to carry this forward. (Cory: this looks like CAI? ref CAI-4608.) Caity is now in another role in the organization. A bug will need to be logged, the issue will need to be reproduced, and it will need to be assigned to the correct team. (I'm not a cumminity manager, I'm just a developer in one corner of Photoshop. And I'm not the right guy to hunt this particular issue down.)
But - from a comment in the ticket above, it suggests that there is "an old style sidecar has the PS preferences ignored". That might be a clue to preventing future creation. (But I don't know since I don't have t his problem.). Also, notes indicates it is safe to delete these side-car files.
... View more
‎May 06, 2024
10:33 AM
Just to be clear, Rick is The Guy for ACR support issues. But he (or someone on the team) needs to be able to reproduce the problem before progress can be made.
... View more
‎May 05, 2024
04:43 PM
2 Upvotes
@Kuttyjoe Might you have installed 24.7.3? That splash screen looks like it belongs to major version 24. I think.
... View more
‎May 05, 2024
04:40 PM
2 Upvotes
I'm not sure what version that is. I've seen the graphic before, but I don't associate it with a version (I've see a LOT of splash screens over the years, some release, some beta, some prerelease, some internal). As far as I know, 25.7.0 is the latest offical release on Windows. The Main branch is currently tagged as 25.9, but it has not yet been moved to Release Staging. I don't ever recall seeing a 25.8 in the pipeline, but I am not sure. I think there was a special release for demonstration at London MAX a few weeks ago, but I'm not sure what version that was; Maybe another Adobe person watching this thread knows.
I also checked the internal communications on offical build release versions. I did not see any mention of a version 25.7.1.
So, I don't know what you managed to install. In any case, 25.7.0 is what we should looking at. And I think 25.9 will be the next official release.
... View more
‎May 05, 2024
02:55 PM
2 Upvotes
So far, I can't reproduce with 25.7. I've been trying for a bit, given what you described, so I'm probably missing some crucial ingredient.
... View more
‎May 05, 2024
02:35 PM
1 Upvote
@Kuttyjoe Let me clarify.
>> Are you saying, if I were to select the hand tool, use it, then switch to another tool, then see if it's still on the hand tool?
I'm looking to see if you get into a stuck mouse-down state without keyboard chording being involved. i.e. Just use the Hand Tool and move things around. Mouse-up. Are you stuck? Or just use the Zoom Tool and mouse-down, sweep left or right, then Mouse-Up. Are you stuck?
Keyboard chording can affect which tool is being used when a mouse-down happens. Event handling properties (for that Tool) are established at mouse-down. If the Tool is switched to an Alternate Tool due to keyboard chording or some other behavior that closely follows the mouse-down, like the mouse being over a special control surface in the document (e.g. a rotate grab handle), then problems may occur, especially if the Tool cursor has not changed yet. I just found a bug with Pen and the Marquee Tool, where if you were working very quickly, and you tried to create a new selection over an existing one, we try to switch to the Move Tool. In that case, we might miss POINTERUP, because the Move Tool only deals with Mouse-based events and is not Pen aware. That's why the precise details of what Tool you start with and comes first (mouse-down or key-down) matters, as if affects how control flows through the code. And it is also why I'm trying to be as precise as I can, because without those steps, we are very unlikely to reproduce. Our muscle gestures may be just slighly different from yours, and you see the bug, and we don't.
As far as your frustrations go, I certainly understand. All I can do is try to find and fix the problem. To find it, I need to reproduce it.
... View more
‎May 05, 2024
01:51 PM
3 Upvotes
@Kuttyjoe Please confirm the following:
Windows (version?) Thanks I see you added that.
No Pen attached?
New default document?
After you open the document, are you in the Move Tool by default? If not, which Tool?
What happen when you don't use a keyboard chording gesture? i.e specifically choose the Hand Tool or Zoom Tool and no space bar or control key on another Tool. (I'm not suggesting this is a fix, it's just data. It is important that keyboard chording works.)
Are you using the keyboard chording at the same instant that your mouse down? i.e. Is it key down and mouse-down at very close to the same instant, or is key down first, see the cursor change, then mouse-down?
It sounds like a lost-mouse-up situation similar to what we've been hunting all this time. After clariifying steps, we'll try to reproduce. If that fails, we'll probably ask you to generate an Event Log file. Thanks.
... View more