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

Question

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

Answer 1

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