We’re winding down Chrome Frame, and plan to cease support and updates in January 2014. Please read the blog post for more information. For guidance on what you need to know as a developer or IT administrator, please read our developer FAQs for Chrome Frame.
This document describes the troubleshooting flow for Google Chrome Frame users.
If the problem has serious security implications please report it using guidelines posted here: http://www.chromium.org/Home/chromium-security/reporting-security-bugs
Before you file any bug, please search Google Chrome Frame bug tracker: http://code.google.com/p/chromium/issues/list?q=Area%3DChromeFrame If your problem is a known issue then it’s likely that a solution is waiting for you. If you find the bug is already there, feel free to star it so you can find it later and indicate to us another person is interested in its resolution.
if you can't find the bug in the database should you consider filing a new one by filling out the form here: http://code.google.com/p/chromium/issues/entry?template=ChromeFrame%20Issue If possible, provide a test page that demonstrates the problem. Test pages help quickly fix the problem and allow us to catch regressions in future.
Asking a Question on the ChromeFrame Discussion Group
Join / post your question to http://groups.google.com/group/google-chrome-frame This forum is answered by Chrome Frame engineers, and is publicly-viewable, so don’t ask any sensitive/proprietary questions here.
Right-click the page (make sure to click on the page, not on any embedded controls e.g., flash). You should see a (small-ish) context menu that shows “About Chrome Frame...” as the last option in the list.
If you don’t see this, then ChromeFrame is not running this page.
Websites are not automatically triggered to load in Chrome Frame -- the site has to explicitly trigger it. In order for a web site to know that chrome frame is available the following should work:
Make sure that Chrome Frame is installed and enabled. Chrome Frame plugs into Internet Explorer as a BHO. When a new BHO is installed, it needs a browser restart to get loaded. However, after a fresh install, a site can use a script on the landing page that makes sure the current browser instance gets Chrome Frame activated.
If a browser restart or reboot fixes this problem then this is very likely a BHO load after install issue.
Example support thread:: https://groups.google.com/group/google-chrome-frame/browse_thread/thread/517755cfbe6d31db
Example support thread:http://groups.google.com/group/google-chrome-frame/browse_thread/thread/438390134edaf4fd#
You have installed Chrome Frame and even after the browser restart or reboot it does not work. Then you can first check if Chrome Frame is installed:
Example support thread:http://groups.google.com/group/google-chrome-frame/browse_thread/thread/21cb36205d1b79a2#
Example support threads:
Example support thread:http://groups.google.com/group/google-chrome-frame/browse_thread/thread/38c53f04d1f6af13#
Example support thread:
Example support thread:http://groups.google.com/group/google-chrome-frame/browse_thread/thread/a49b91141fc84a10#
Google Chrome Frame plugin is loaded as npchrome_frame.dll in Internet Explorer processes. It uses Chrome’s multi process architecture so when a web page is loaded using this plugin, it will launch a Chrome Browser process, which in turn launches a Chrome Renderer process.
The following sections describe how to identify crashes in these processes.
In this case Internet Explorer will detect a crashing plugin and put up a dialog like this:
More detailed information about the crash can be added by clicking on the ‘Advanced...’ button to bring up the crash details dialog and inserting the details in the bug report .
If for some reason the Chrome Browser process crashed or lost connection with the plugin running in Internet Explorer, then it looks like this:
To figure out if this is a crash use the following steps:
If a Chrome Renderer process crashed with Chrome Frame then it will look like this:
It’s very rare to have Chrome Frame specific renderer crashes. So the first thing to verify is see if the same steps lead to a crash in stand alone Chrome browser. In either case, a test page that demonstrates the crash will be really helpful in the report.
While reporting a crash, having a reproducible test case is very important. If the crash is happening at random then having a crash dump is quite useful.
A freely available tool called ‘Debugging Tools For Windows’ (32 bit download 64 bit download) or ‘WinDbg’ in short, can be used to collect crash dumps. Once you have downloaded and installed the correct flavor of WinDbg then run Internet Explorer under the debugger using the command line:
or for 64 bit OS use:
Now switch to Internet Explorer and follow steps to reproduce the crash. Note that once the crash happens, you will not see usual dialog or ‘sad tab’ bitmap. Instead, Internet Explorer will appear unresponsive. When that happens, come back to WinDbg and it should look like this:
Type the following command into the debugger prompt as shown in the picture above and press Enter:
After the crash dump is successfully written to the disk please attach it to the bug.
Sometimes Chrome Frame may not work as expected due to spyware or other buggy Internet Explorer Add-ons. To make sure that is not the case, it’s best to test on a clean Windows image. Also, for the purpose of testing, any other installed Add-ons can be disabled by going into ‘Tools’ -> ‘Manage Add-ons’ dialog in Internet Explorer.