P: "Adobe Community Help" keeps popping open (Windows)

I take the 1366 x 768 back, one machine is 1920 x 1080 and it does it too.

Then how about someone lends Adobe his System, or give em access to the system!?

Garconis - first we'd have to have some idea what we're looking for. We can't capture everything about your system without having your system in hand. And right now we have no idea what about your system might be triggering this -- it could be almost anything (utility, app, driver, bad hardware, a preference in something, etc.). It may not be something obvious, but there has to be something in common between your systems.

We are not mind readers - you have the system with the problems, and we do not. Despite being released software, we cannot anticipate all bugs in other applications or even all the bugs in the OS. Right now we need some idea of what to look for, or full time access to a system that shows the problem often.

Again, we would like to see this fixed - but it's very rare that we can fix something that we cannot see or reproduce.

I bet I can make any Windows x64 machine you have do it.

The only thing our computers have in common is 1366 x 768 monitor resolution (different monitors on each machine).

I have tried with several machines, completely clean installs of Windows XP, 7, 8 (all x64) with minimal hardware and only video drivers.

I can trigger mine almost anytime at will on every single machine I've tried.

Write something for us to run on our PC that can hopefully capture/store information -- say 5 minutes before the event was triggered -- so it can help determine what processes were running during the trigger, etc.

Another note...we shouldn't be asking ourselves anything. You should be asking us the things. We're trying to trouble shoot YOUR program that WE already paid for. This isn't a beta...

If you need more information from us to help you solve an Adobe bug, then tell us what you need us to do. Don't expect us to just give you what you need. Help us out, so we can help you. Again, this isn't a beta program...but we're willing to help...but don't expect us to solve your problem for you. This is a serious bug to a "minority" of Photoshop users, that Adobe needs to take more seriously. Time (and money) has been thrown out the Windows (almost literally) due to this bug.

It is possible that the remote connection changed something about the behavior of the system (we have another bug where we think that actually happened - because Flash was busy during the remote connection). But it is also likely that the problem is intermittent and just didn't happen during the hours that we spent working with them, or that it just doesn't happen as often as people remember it happening.

One thing to ask yourself: who do you see it so often when the vast majority of users (including many power users) never see this problem. What is different about your systems? What utilities do you always install? What OS settings do you always change? Was the OS an upgrade or a clean install?

Odds are that this has nothing to do with "pressure", but with some utility or other application injecting events to the wrong event target (which would invoke the help request). But we've tried all kinds of things, and not reproduced this inside Adobe.

And we have seen some screen captures/recordings - but so far they have offered no new information about what else was happening on the system to trigger the problem.

One should also point out that the creator of this topic (a user who experiences this issue on a sometimes weekly basis) was never contacted to assist Adobe's quest...

I don't think I'm putting Photoshop under a lot of preassure, since I'm only at 1024x768 with 32bit colors ("Real colors" - translated from Danish).

I can of course not comment on how the others experiencing the problem trigger it, but whenever I trigger it, it is always after a LOT of repetitive work (selecting two colors with the color picker, then opening the color picker tool for each of the colors and adjusting the selected color slightly, then clicking OK before using the brush tool - repeat this for around an hour and Photoshop pops up the Help window).

As the help window is just a local HTML file, I have thought about just renaming this file, but i hesitate to do so, since those times it has been possible to continue working without restarting Photoshop after the "Help Explosion", the program has become unstable after some time resulting in some sort of memory error where it is not possible to save the work I have done. In this case I would rather just restart when "warned" by the help window popping up.

Added: Perhaps some of the people experiencing the problem could film their working process and the problem appearing? I know it wouldn't give you any data, but it would show the user behaviour.

One of the things the remote connection does is reduce display settings (to reduce bandwidth needs). So we can try reducing the screen resolution, color settings, etc and see if that changes the behavior.

So creating a remote connection solves the problem?
That is probably something you should look into, since the remote connection probably has some sort of effect on memory handling etc.

Were the people you contacted having the problem on a regular basis (not just once or twice), and did the remote connection make it absolutely impossible for these people to reproduce the problem? I'm serious: This should be looked into.

I have had the problem on Photoshop 4, 6, 7 and CS (my current version) on four different computers running Windows 95, XP, XP and 7. It always happens when I use the Color Picker, and usually happens after 1⁄2-1 hour of work. To be clear: It has happened on EVERY SINGLE computer and with EVERY SINGLE version of Photoshop, I have ever used.

I'm sorry, but I don't think this is connected to a non-Photoshop application, but in stead to some very specific patterns of user behaviour, that are probably just a bit too intricate to register and thus easily reproduce. If this really only happens to very few people, and you claim that it is connected to some type of application that is NOT Photoshop, it should be impossible for it to happen to me on four different systems with four different versions of Photoshop.