I just updated to the 4.1 version in windows 7. I had shortcuts on my display fusion taskbar for chrome default and an app shortcut for chrome that linked to gmail. now with the update to merge the shortcuts with the active windows icons whenever I move a chrome window or a gmail window onto the display fusion taskbar it will merge with one of the shortcuts and remove the other one not necessarily the one that matches it either. if I move the window to my other monitor then move it back it it will restore both shortcuts then remove the other shortcut. last if I move a chrome window onto the display fusion monitor I get 2 gmail icons.

Thanks that would work for now. I wonder how google got them to separate in the first place.

Chrome is still moving around for me... is that happening to others?

I pin it to the taskbar, and then a separate (and unpinned) one eventually gets "generated" at the end.
All attempts to kill it, just result in it eventually happening again. I guess I could live with 2 chrome icons, one being like a "Quick Launch - like thing", but it just an annoyance.

it's supposed to work better in 4.2 but that's still beta

Yes

I have pinned Chrome to the taskbar in Windows 7.
When new chrome windows are opened, "eventually" another icon for chrome gets created at the end of the taskbar (after other window icons, like pinned ones).

As more chrome windows are opened and closed it eventually becomes that all chrome windows are stacked under the 2nd unpinned chrome icon, and the pinned one, is simply showing nothing. When clicking on the pinned one, a new window will open, and then the pinned icon will indeed show a window belonging to it, but most are shown under the unpinned one.

I am not sure how they are "shifting" ownership to the other icon, but it is definitely happening somehow. The temporary fix it to close all chrome windows, unpin the pinned one, and then pin a different one for chrome. But eventually it always goes back to this problem .

See if you can recreate this with the latest chrome. Pin it to the taskbar, and open some windows. It eventually happens, where a 2nd, unpinned one is created.

Same thing here. Ok, I will try and screen record it, and post back here, when I get some free time in the next few days. I will post back here with it, to see if you can replicate it from what I am doing.

Video:
http://www.youtube.com/watch?v=8AM1poCFIbQ

I am using Ctrl+N for New Window

Combinations of Pinning and Unpinning. Doesn't matter even when moving around. Always happens when another window is created, typically with Ctrl+N.

Play around with it and I bet you can make it happen

Sorry I just now saw this. There is no command line parameters for chrome. I guess I could try and see what happens on a fresh install of Win7 to see if the same results.

Definitely the most current.

Mine says, Version 22.0.1229.94 m

I have been playing around with different positioning in the task bar (start, end, middle), but the same still results.
No other extension in explorer should be conflicting with it either. Using Process Hacker (or Process Explorer) to view the loaded modules in explorer, I mainly just see extensions that should conflict: Dropbox, Unlocker, some from Apple from iTunes / Bonjour, and NVIDIA.

This is an x64 system btw.

I am curious if others experiencing this issue also.

Something must be triggering DF to think that it belongs elsewhere though.
Should be based on the Executable's path, at least that is how Explorer.exe does it if I am not mistaken (new button for a window, if the Exe is located at a different path). But this is the same chrome here...
C:\Users\Alt\AppData\Local\Google\Chrome\Application\chrome.exe

And from Process Hacker, having it map each window to each process, they are all owned by the parent chrome.exe process, so there isn't any difference there.

Very confusing indeed.

I appreciate it. Thanks man!
This one is definitely bugging the hell out of me

Keep me / this topic posted

One other thing to make note of that I just discovered.

- The behavior occurs when DF is running
- After the Pinned chrome shortcut is experiencing the behavior, then even after I have DF exit, the same behavior is still exhibited! (meaning DF some how damages the pinned icon -- where new chrome windows will launch in a new unpinned item)

I found this interesting indeed.

That is correct. Even after I Exit DF. Its like it "breaks" the shortcut / pinned icon... and even after DF stops running, explorer still creates a "new" unpinned icon, and refuses to group it under the one I clicked on (the pinned one, that is now "broken"... apparently by DF, because it only happens once DF runs).

Odd huh?

I will try this and get back to you on it.

Yes, it still does! So it really is broken...
I think I need to investigate into the internals of how explorer determines its icons. Actually, you may know better.
If you give me an exe to run, and have it dump out output from those buttons, maybe we can see what explorer is thinking this icon is.

Im sure you have the code that you could break out into some test app and have it dump out stats about the icons, so Ill run anything you want, and send you the info. Maybe then we could figure out what DF is doing to this icon, to make explorer mess it up / treat it differenty.

I have a much better video demo for you now. Watch this:
http://www.youtube.com/watch?v=qCExI03sti8
(its easier to see my text in notepad, if you select "Large Player" and "480p")

If I get time, I almost want to just try this on a VM, AND also on a test Win7 x64 HDD partition for a clean system, and see if the same behavior is exhibited.

Just as a sanity check, here are all of explorer.exe's loaded modules (from Process Hacker), sorted by Company Name (the 2nd column/item)
http://pastie.org/5117481

But its nothing that should be causing this... (most are Microsoft, obviously, but the ones that are not, shouldn't have anything to do with the taskbar).

Right now, I think the best thing to try would be to get a detailed "internal" list of what explorer.exe things this "icon" is.
I think this could be easily done from some code from you that you could compile into a binary, and send over, and ill run it, and send (and look at), the results... see if this is truly different.

You can hack up my explorer.exe's memory all you want , esp if it leads to figuring this out!

Hmm that is strange.
I was under the impression that this is only happening after I run DF.

I am only user in chrome (it even says so: "You are currently the only Google Chrome user.")

I may try doing some other tests and see.

I am so sorry for the confusion. I thought this was DF's fault, but it was not at all.
See here: http://code.google.com/p/chromium/issues/detail?id=91650

It is indeed caused by multiple user accounts.

The fix:
You have to exit Chrome, go to:
C:\Users\<USER NAME>\AppData\Local\Google\Chrome\User Data

And delete the "Local State" file.