I am the developer for a large enterprise website, after the upgrade to chrome 32 the website stopped working completely. I Get the 'aw snap' about the time we have to render most of the elements on the page.
Its a massive code base so i haven't been able to find what's causing it. Ive been booting chrome in debug mode and watching the logs there.
Wierd behavior:
1)If i disable flash it works, we are using swfobject with a flash library.
2)I sometimes see in the logs when it crashes "Uncaught RangeError: Maximum call stack size exceeded" so i must have a infinite loop, but its not a always thing.
3)If i refresh enough it will boot all the way up, and work for good until i kill tab and start over. But again thats a sometimes cause it may start the crash cycle again after a few refreshes.
4) I sometimes see the error "file_descriptor_set_posix.cc(22)] FileDescriptorSet destroyed with unconsumed descriptors" Which i think relates to a infinite loop in the rendering of the webpage which would relate to the maximum call stack exceeded error.
Does anyone know what has changed in Chrome Version 32 that would be a good starting place to find the bug?
Libraries used: SWFobject, Backbone, underscore, soundmanager.js
I dont know why this fixed it, or what chrome changed that caused the code to break but if anyone is interested in what we did to resolve the error i'll explain.
1) I made all events going out of swfobject and our swf code go directly to the Flash.js class we had to interface with flash. Before it was propagating through a Backbone.dispatcher to the flash class. That caused the aw snap error to go away.
2) We were using a datetime library called Moment.js version 2.2.0. It was the one throwing the maximum call stack error, after updating that to 2.3.0 it stopped. Would love to know what chrome changed to cause a infinite loop.
If anyone has info on what chrome changed between the two versions that caused either error, I would love the answer because its a bit scary fixing the symptoms but not knowing the cause.
chrome will open multi tasks in the task manager, and it is sensitive to many plugins
try the following
1- go to settings in chrome
2- open extentions
3- disable all the extensions that you can
4- close chrome
5- open task manager in windows
6- go to processes
7- close all the processes related to chrome
8- reopen chrome and check your problem again
Related
I'm working on Chrome extension which needs to perform an action just before Chrome closes. Is there any method like chrome.window.onClose.addListener(...), or chrome.runtime.onClose.addListener(...) to ensure that something will be done and then chrome will close itself?
I've been struggling with this problem for two weeks. Here are the options for potential solutions that I've found, but they didn't work.
My investigation results:
Using function: chrome.runtime.onSuspend.addListener(...) - I don't know why, but it doesn't work at all for me. For example, I've tried to write a callback for this event, which tries to add hardcoded data to the indexed DB, but it doesn't add it. Description of this method even says that the callback is not guaranteed to be completed. OnSuspend documentation
Sent to the event page just before it is unloaded. This gives the extension opportunity to do some cleanup. Note that since the page is unloading, any asynchronous operations started while handling this event are not guaranteed to complete.
Chrome working in a background - with this option my extensions seems to work, but... only on Windows older than Windows 10. I've checked few options and on my other computer, which has Windows 7 installed, processes connected to Chrome are closing more slowly, which gives time for my extension to perform necessary tasks. Unfortunately, Windows 10 kills all the processes much faster. I've check option "continue running background apps when google chrome is closed", but it doesn't change anything. I've also enabled flag "#enable-push-api-background-mode", it hasn't helped either.
Keep Chrome running in the background on Win10, Enable flag to keep Chrome processes running
chrome.app.window.current().onClosed - I've found a similar question on Stack Overflow, and one of the answers was the code mentioned above. The problem is when I try to type chrome.app.win... inside console, it doesn't show any suggestions both in background script and content script. Google's documentation doesn't mention any permission that I've to add inside my manifest.json to get access to this functionality.Stack Overflow similar question, Google's documentation about chrome.app
Methods build in web browser - I've thought that method window.onclose might be useful in my case. I've performed the same test as for chrome.runtime.onSuspend, but the result was exactly the same. Documentation
I've stuck and haven't got any idea how to solve my problem. Maybe I missed something important? Hope you will help me.
I'm having this weird issue when exporting my Unity 3D application to webGL. On my computer it runs fine (on Unity, that is) but when I put it online it gives me the Maximum Call Stack Size error on Chrome (firefox runs fine)
I did some research and most articles say it's because of a possible infinite loop on the code, I checked my code and there are no infinite loops (it would hang on firefox). So now I'm not sure how can I debug this. Can someone help out?
Update: I tried disabling objects from the scene, and even with an almost empty scene with no C# code running, it will still return this bug.
I had this error. I was able to fix it by just refreshing the browser cache. Ctrl-Shift-R wasn't enough on Firefox. I had to go into network console enable "Disable Cache" there.
Thanks #slaw. It did not work for me by refreshing, but when I opened it in an Incognito mode, the error was gone.
Using latest Unity 2018.1.0f2 Personal this was happening. File --> Build Settings --> WebGL --> Player Settings - select WebGL Build. Then on the inspector tab changed the Api Compatibility Level from 4.x to .Net Standard 2.0.
All working now.
Error in Chrome
Uncaught RangeError : Maximum Call Stack Size Exceeded
Error in Firefox
Too much Recursion.
I am getting this error only in Safari and Chrome on Mac machine, but can't reproduce on other browsers nor on Windows.
The main problem - there is no information on what function caused the issue. No stack trace with most recent calls before the exception. And even the "Pause on exceptions" setting is not working. It's not paused on this exception, only puts the information to console.
How can I troubleshoot what is causing the issue, on what function it crashes, what was the call stack before crash?
Or how can I log all the function calls(important note, the profiler should be started immediately after page load).
I have managed to find the point that was causing the error, so here are some advises for those who will face a same issue:
console.log is your friend. I haven't found an option in Google chrome that will trace all methods calls starting immediately after page load. Even if there is such setting, the amount of calls you will see maybe really massive. So you can use console.log to log whenever one of your functions called.
Commenting out parts of the code. In my case the js file was really huge and it was helpfull to find at least the part of the code that was causing an error. So I started by safelly commenting out the code piece by piece.
Using technichs above I have found that the issue appeared in the obfuscated code, so next thing I tried was disabling obfuscation options one by one. With this approach I have found that issue appeared when enabling 'string splitting' obfuscation option. Also I have found these issues on a code.google.com chromium 446047 and 56588.
I'm getting EXC_BAD_ACCESS crashes in a WebThread, while my app is trying to process some javascript on a page startup. The javascript is long and involved and is probably what's bringing this down. The only hint is that the call stack says it's happening in WebCore::StorageMap::key(unsigned int). Can't debug it in the web debugger because it crashes on page startup so I never get to a point where the page can be selected in the developer menu. Has anyone seen an error like this, or have a good way to track this down?
We finally figured out what was wrong. There were two pages - both used a third party Javascript library. When you ran either of them, it was fine. It was only after you ran one after the other where the second one crashed. The reason was although they were running the same library, they were running different versions of the same library, which stayed resident in cache. When the second page tried to run the library of the first page (because it was still in cache) it crashed.
i have built a HTML5 web site (or rather webapp as you wish) and it works fine in Chrome and firefox. I would say the only thing out of the ordinary is, that it uses
Google Closure in some parts (the issue persists in the simplest, non-optimized mode)
HTML5 canvas for 2D drawing
Now I was curious whether it would run on my Galaxy Tab Tablett and indeed it does. I was able to set up the remote debugging facility https://developers.google.com/chrome-developer-tools/docs/remote-debugging?hl=de and debug my code to get rid of a few things that were not working properly. However I notice that android-chrome regulary crashes while I use my app. The console in my desktop browser then complains about websocket being closed (thats why I suspect it really is a problem of the tablet side).
I would like to know what makes my website crash and am a bit flubbergusted that my HTML/js site can crash a browser like chrome so easily. I would have thought that it should be more stable than that.
Now as I would like to have an "entry" point into debugging the issue:
is there a crash log of chrome for android that I can inspect somehow?
can I somehow make it (chrome or android in general) more verbose on error messages?
There are a couple of things that you can do:
chrome://crashes will list the crashes that it has caught when a tab crashes - you might need to turn on crash reporting in the settings. You won't be able to fix it but you will be able to report it us so we can see if it is an issue.
Use logcat and see if there are any specific issues in the tracing output, such as an out of error message.