P: Completely broken Hand tool (PS24.5) Hand Tool Sticking, sticky, not seeing mouse-up

Rarely sign in here, but just updated photoshop to the latest version and immediately encountered this issue.

Reading the responses of employees does not fill me with confidence. Rolling back. Sucks as I was excited to try the new AI features but not if I have to struggle to maintain control of the artboard to do it.

Hope you all get a solution. Will check back next time an update piques my interest.

We really don't have an idea of how many people are affected, but it's probably < 1%. Unfortunately, if you are in that category, that is an extremely unhelpful bit of data. <<<

I've done everything I could as a writer of this thread because I have absolutely no knowledge of programming and have difficulty providing clues any more. Same with recreating it as a YouTube video.

So I understand even if this bug is hard to fix. However, I can't agree that some of you are experiencing this bug.

Most ordinary people don't even know if it's a bug or not. To know if it's a bug, you need to know what it's like when Photoshop works normally, and among those who know it, I only write on the forum for some users who want to see it fixed.

Dozens of people in my team and I have had the same bug reproduced on dozens of computers. (Not only this bug, but also the ones that were reported before and eventually fixed.)
So even if 10 out of 10 people are reproduced, is this still 1%?

The expression "some users" at least doesn't seem to suit bug reporting threads.
Most users experience this, and they don't know if it's a bug or not.
That's what Photoshop is supposed to be like. It's supposed to be this sticky. It's supposed to be this slow. Photoshop is supposed to crash once in a while.
Most people think like this about all previous issues or bugs, so they don't report much.

> There are probably way more people affected, but I can picture only 1% of us actually sign up to the forums and complain about it.

Yes, I am severely doubting this 1% figure. Given the number of reports and the fact that this has been going on for years, that there are literally dozens of threads, and these are only those frustrated enough to take the time to make an account and report it.

In any case, it needs to be fixed. It's gone on too long.

Sounds like a lead then: what areas do you not collect? E.g., one thing I note is that this happens on all of my systems, but I use a Logitech MX Anywhere Bluetooth mouse with all of them. Perhaps this is related (i.e., maybe it is a bluetooth issue).

In any case - given that I have experienced this issue across 5 different hardware sets (all of them), if the mouse is not the problem, then this is a common issue that has just been neglected and not something that very few users experience. If I can reproduce it on all 5 of my systems, this is a regularly occurring issue.

Regarding mouse down - I have never noticed lost mouse down events. It is always losing the key release.

In light of that, I think it would be all the more valuable to find a way to put together some kind of standardized template, web form, ect. So that we can find what those of us who are experiencing the issue have in common. 
 I know this has been mentioned in the past though thus far there seems to be no appetite to attempt such a thing. However, I think it would be more efficient to have everyone follow the same template and then submit their info, rather than everyone posting their own creative account of their issue. Not to mention that some are not native English speakers so, any formatting help could make a significant difference in their participation.

> I am willing to share the information from my system if someone could tell me (not very tech savvy) what is desired (for, example, PS: Help: System Info)

Thank you. Unfortunately the System Info that Photoshop generates has not offered us any clues as to what might be special about affected systems. Whatever and wherever the problem is, it's in some area where we don't currently gather data.

I have this problem and thus have been following this thread for months. In an effort for Adobe to collect as much data as possible about who is affected, I am willing to share the information from my system if someone could tell me (not very tech savvy) what is desired (for, example, PS: Help: System Info) and exactly where to post it online.

Whereas I share MUCH frustration with not being able to use the latest versions of PS (while auto-paying my subscription), I do appreciate Adobe's engineers continuing to try to help us who have this problem...

The less common a bug is, other things being equal, the harder it is to track down and the smarter (and luckier) the investigators must be. And in modern systems it's seldom one thing: it's some rare combination, perhaps a subtle timing issue involving multiple vendors and APIs. 

The worst-case troubleshooting scenario is something that affects only a tiny number of installations and is intermittent. They're really, really hard to crack.

I don't work for Adobe, never have, but I've beta tested drivers and apps for various companies over many years. Here's my perspective, hopefully somewhat useful. Apologies in advance to the folks who already know this stuff.

Good engineers, in my 40+ years of experience, care deeply about the code they work on. It's personal. They talk about "owning" a module or a section of code, and they mean it literally. Uncaring or incompetent programmers, far less entire teams, don't survive at high-end companies. Skilled engineers who care about their work are the ones who last, so it's safe to assume that the people on this hunt put as much importance on finding the answer as anyone in this forum. Are the Photoshop team brushing this off? No. If they were, they wouldn't be on the team.

Why is it taking so long to fix? Think of it as an escape room: you can't even start to solve it until you pay for your ticket and they let you in. The first step in bug hunting is finding a way to reproduce the problem, and a bug you can't reproduce is an escape room with no way in. The Photoshop team has hundreds of individual test systems, but there are many millions of possible configurations. Collectively, the team probably shares a couple of centuries or more of engineering experience, but they aren't clairvoyant.

What's our role, then, since we can't work directly on the code? -- To provide them with all the data we can dig up. Rants won't help, information will.

Every report helps to narrow the search. "I did [x] and the problem went away, but after [y] time doing [z] it came back." "It showed up right after an OS update." "I have tried x, y, and z workarounds with/without success." "My CPU/GPU/chipset is [x]." "My system is [hardware detail], OS version, app verson(s), Human Interface devices, driver versions, update history."

A few folks have commented along the lines of, "You should fix this! You're not even trying!" or worse. Besides being (at best) disrespectful, that kind of remark doesn't belong on a professional forum. We are more like pilots than passengers; collaborators more than consumers. We can't all add Spy++ or other deep instrumentation, but if everyone who sees the bug reads @CJButler's pinned post and provides what info they can, one of those reports may contain the key that unlocks the escape room, so the real bug hunt can start.

Please refer to the pinned reply. That reflects our latest information.

We have observed the bug on user machines. Observing the behavior has not been sufficient to diagnose the cause.