Comment #30 on issue 3126 by ja...@codetorque.com: Open link in live messenger will launch chrome.exe but chrome window cannot show http://code.google.com/p/chromium/issues/detail?id=3126
I have this problem also. Windows Vista 64bit Chrome 1.0.154.48, set as default browser Most of the time, links in external applications launch chrome fine. If no copy of Chrome is running, and I click a link in Live Messenger, however, I get a chrome.exe launched, and a status bar appearing briefly on the screen, but no browser window appears. Worse, this 'invisible' chrome.exe then swallows all subsequent requests to display web pages from external applications. (I don't get the behaviour described by cwt.tong of subsequent launches showing a window with the previously-opened page as a tab) Let me follow through a scenario (with the help of procmon.exe's process activity summary), triggering chrome from URLs in two different external applications - twhirl.exe (a 32bit twitter client) and Windows Live Messenger (msnmsgr.exe). Initially, chrome is not running. 1) click a link in twhirl.exe: A chrome.exe is launched by twhirl with the command line "C:\Users\ABC\AppData\Local\Google\Chrome\Application\chrome.exe" "http://twitter.com/someusersprofile"; It in turn launches a child chrome.exe with the command line: "C:\Users\jamesh\AppData\Local\Google\Chrome\Application\chrome.exe" --lang=en-GB -- type=renderer --channel=280.8bc0f8.1431390593 And, most importantly, a Chrome web browser window appears showing the expected page. 2) now, with that browser still open, click a link in msnmsgr.exe: A chrome.exe is launched by msnmsgr.exe with the command line "C:\Users\ABC\AppData\Local\Google\Chrome\Application\chrome.exe" "http://some.lolcat.site/someone_sent_me.html"; now the -first chrome.exe (not this one)- launches a child chrome.exe with the command line: "C:\Users\jamesh\AppData\Local\Google\Chrome\Application\chrome.exe" --lang=en-GB -- type=renderer --channel=3012.2b1e300.1881274863 The chrome.exe launched by msnmsgr.exe exits. 3) close the web browser, check in task manager shows, no chrome.exes are left running on the machine. So far, all is behaving as we would wish. Now, let's launch the same two websites from msnmsgr and twhirl in the reverse order: 1) click the link in msnmsgr.exe: A chrome.exe is launched by msnmsgr.exe with the command line "C:\Users\ABC\AppData\Local\Google\Chrome\Application\chrome.exe" "http://some.lolcat.site/someone_sent_me.html"; It in turn launches a child chrome.exe with the command line: "C:\Users\jamesh\AppData\Local\Google\Chrome\Application\chrome.exe" --lang=en-GB -- type=renderer --channel=280.8bc0f8.1431390593 the status bar flashes up, but no chrome window is launched. Both chrome.exe processes remain running, but invisible. 2) now, click a link in twhirl.exe: A chrome.exe is launched by twhirl with the command line "C:\Users\ABC\AppData\Local\Google\Chrome\Application\chrome.exe" "http://twitter.com/someusersprofile"; now the -first chrome.exe (not this one)- launches a child chrome.exe with the command line: "C:\Users\jamesh\AppData\Local\Google\Chrome\Application\chrome.exe" --lang=en-GB -- type=renderer --channel=3012.2b1e300.1881274863 The chrome.exe launched by twhirl.exe exits. three chrome.exes are left running; no chrome window is visible on the screen. Launching a new chrome.exe directly launches a browser window; viewing Chrome's task manager shows the previously opened pages listed as Tab: tasks, complete with favicons and titles (suggesting the pages have loaded even though no renderer is displaying them). The tabs remain inaccessible from the newly launched window however. double-clicking in the task manager doesn't magic them into existence either. Closing the newly-opened chrome.exe also doesn't close the already-running chrome.exes. If I kill off the invisible tab tasks through the chrome task manager, then close the chrome window, I'm still left with one chrome.exe running (the one originally launched by msnmsgr.exe), and launches of chrome.exe with a specified URL continue to exhibit the same behaviour - status bar flashes onto the screen, no window is launched. All this, in spite of the fact that both applications appear to have launched chrome.exe in an identical manner. I've attached the requested registry-setting files (all of which seem to reference firefox, not chrome); those in the wow64 subdirectory were obtained running the reg commands from a c:\windows\syswow64\cmd.exe prompt; the others from a 64bit cmd.exe. Hope this helps you confirm and identify this issue. Attachments: reg.zip 3.2 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
