I'm getting the "Aw Snap" message consistently in Chrome when performing the following:
Load a page that displays a silverlight rendering
Click on a button that fires off a fancybox containing an iFrame that contains the same Silverlight rendering
Close the fancybox
Receive the dreaded "Aw Snap" message
Reload page and page loads up again
Notes:
This does not happen in IE
This does not happen in Firefox
When I go to chrome://crashes/ there is no record of the crash
Chrome Version: 24.0.1312.57
Silverlight Version: Silverlight 5 (5.1.10411.0)
Searching through Google's Chrome issue board yielded very little and any issue reported that was similar was either years old or did not have a response. Hoping that someone has encountered the same problem and has a workaround.
Related
I am trying to solve a mystery:
A page from a React web app can be loaded in Safari on iOS
That page can be loaded in Chrome on iOS if you choose "Request Desktop Site"
That page is blank when attempting to load it in Chrome on iOS if you go with the default "Request Mobile Site"
The page works fine in desktop browsers
I have taken steps to enforce a timeout on the server side, in case there is a connection that is hanging. But when I consult the logs, the requests complete quickly without any of the usual follow-on activity. My guess is that there is a JavaScript error of some kind that is causing the React app to bail.
What is a good next step that might be helpful in troubleshooting this issue?
ETA: Added new information that confirms the requests are making it from Chrome to the Golang server, as expected.
I think what's going on is that the "Request Mobile Site" mode falls over when there's a large JavaScript bundle, whereas the "Request Desktop Site" doesn't for some reason.
For anyone who runs into this situation, something that worked for me was to decrease the amount of JavaScript that the iOS Chrome app has to load, e.g., using code splitting, user agent sniffing and redirection to a less memory-intensive page in the case of iOS Chrome. After doing this, things worked fine. I'm guessing that less memory is available to apps running in the "Request Mobile Site" mode than in the "Request Desktop Site" mode.
I have made a webpage using Polymer. The webpage doesn't open on Google Chrome (both Windows and Android). When I try to open the page, Chrome shows "He's Dead, Jim!" message on Windows and "Aw, Snap!" message on Android. I have reset the settings and reinstalled Chrome but the problem still continues. Can anyone tell me how to solve this problem or the reason behind it?
https://www.googledrive.com/host/0B2Zii8voDW6QcGduNnl1cFBReXc/fold/
maybe you can check if there is any error in your page, which stop polymer initialization:
https://www.polymer-project.org/docs/polymer/debugging.html#unregistered-element-bookmarklet
Btw, did you try the official demo page with your browsers? If they work, then it's your code problem.
I am experiencing an issue with opening a Microsoft Office Document, using IT Hit WebDAV AJAX library, in latest Chrome 39.0. running on Windows OS. It is a sporadic issue that occurs only in Chrome, and it happens when one opens a document multiple times. Word instance won't start, the page freezes and browser becomes unresponsive, and Chrome suggests killing the page. The only solution is restarting the browser, which solves the issue.
I have tried opening a document in Chrome on Mac OS X, and it is working fine. So are Mozilla and Safari on all operating systems. It seems to be a Chrome + Windows issue only.
Has anyone experienced this issue and is there a fix?
The Microsoft Office plug-in that opens the document displays a warning popup "Some files can harm your computer.", which is a modeless dialog:
If you quickly click on a link that opens the document more than one time the dialog will hide behind the main web browser window. As a result the web browser window is blocked.
You need to switch to that dialog and confirm or reject document opening, otherwise after some time Chrome will ask you if to kill the page or wait.
Note that there is no way to avoid that dialog, this is a built-in MS Office functionality as far as I know.
Chrome will only work good with ITHitWebDAV if the user has got Office 2013 or superior.
Google is blocking all Java applets and NPAPIs now, so good luck with that. I just detect the browser of the user that wants to edit a document, and if it's chrome, I warn him to change to another browser like Firefox with a modal, and that's all.
Very poor support between Chrome and ITHitWebDAV, and no much you can do about it.
So, I have an HTML page that includes a Silverlight xap file which plays a video. It works correctly while running locally and on our DEV environment when using Chrome or FF. The issue is when I am trying to view the video on our DEV environment using Internet Explorer. When doing so, it prompts me to Display Mixed Content. Whether I hit Yes or No, the browser crashes. I am able to go into my options and Enable Display Mixed Content, which fixes the issue and the video shows up correctly on the DEV environment using IE. But, this is not a good solution for a client facing site. Is there a way around this message to prevent it from crashing the browser?
A workaround for this is to use JavaScript to open the HTML page that contains the video in a new window. The user will still be prompted to Display Mixed Content, but it will not crash the browser and the video will play.
For the past couple of days we've been experiencing problems with web pages using Google Maps API V3.
Originally I thought it was one particular page on our website, and have spent at least a day trying to find the cause.
This morning I found it was any page with a map on our website, and have just found it's any page on any website with a map.
We are using IE8 on Windows XP, the problem is that on a page with a map is refreshed IE8 crashes.
If "Enable automatic crash recovery" is on in Internet Options/Advanced then you'll get a "balloon" error:
This tab has been recovered
A problem with this webpage cause Internet Explorer to close and reopen the tab.
If "Enable automatic crash recovery" is off, the usual "Internet Explorer has encountered a problem and needs to close" message box appears, but clicking Debug just closes IE.
This happens on the simple example page from Google, it will load fine, press F5 and IE will crash.
https://developers.google.com/maps/documentation/javascript/examples/full/map-simple
This only happens on IE8 on Windows XP. IE7 on XP and IE9 on Windows 7 are fine, as are Firefox and Chrome.
Can anyone else confirm this, and have any idea how to resolve?
Thanks,
Mike
Update:
Have found that it works fine if XP is started in Safe mode with Networking