Joe Weinpert
asked on
Google Chrome Crashes Aw Snap ran out of memory
I created a webpage that uses JQWidget to produce 3 graphs. The page displays fine initially but as the graphs refresh to display new data the Google Chrome crashing due to it running out of memory to view the page. (bug doesn't occur in Firefox or Chrome)
Aw, Snap! Google Chrome ran out of memory while trying to display this webpage.
I realize the graphs might use a lot of resources but I only have this issue in Chrome even after I clear the cache.
Aw, Snap! Google Chrome ran out of memory while trying to display this webpage.
I realize the graphs might use a lot of resources but I only have this issue in Chrome even after I clear the cache.
David Favor
Post the URL of the page generating the memory error + likely someone can assist you.
Curious if Flash or other needed interfaces need updates
When I last used Chrome had similar issues since each plugin and extension creates a chrome.exe process. Perhaps minimizing those extensions or plugins when graphing will help you. Good luck.
Asta
Asta
ASKER
Unfortunately I am not able to provide a link to the offending site. The page is on the company Intranet.
I was just wondering if anyone has run into a similar problem.
Asta Cu, Thanks for the suggestion. I check my browser for extensions and plugins. I have no plugins and I turned off any extensions and got the same results.
I was just wondering if anyone has run into a similar problem.
Asta Cu, Thanks for the suggestion. I check my browser for extensions and plugins. I have no plugins and I turned off any extensions and got the same results.
Does it happen only when generating multiples at one time? I'm unfamiliar with the program and whatinterfaces might be required nor how many Chrome.exe processes are running concurrently at cause.
This tend to happen with poorly crafted pages which cause Chrome to... run out of memory...
The fix is to fix the code on this page.
One way you can track this down is to download the entire Webpage locally + then start removing Javascript files, till the Aw Snap message disappears. This will tell you the exact .js file causing the problem.
The fix is to fix the code on this page.
One way you can track this down is to download the entire Webpage locally + then start removing Javascript files, till the Aw Snap message disappears. This will tell you the exact .js file causing the problem.
ASKER
Is there an error log or something I can access? I tried following the code in the debugger, but when the page dies, so does the debugger.
The easiest way to track this down is as I mention above.
Start stripping out .js files one by one, till problem disappears + you have your culprit.
You're exactly right about the debugger. Once you run out of memory, everything circles the drain.
This type of problem is far easier to fix via brute force stripping out of individual .js files than trying to use tools to diagnose.
It ain't pretty + single .js file stripping is the last ditch approach that always works.
Start stripping out .js files one by one, till problem disappears + you have your culprit.
You're exactly right about the debugger. Once you run out of memory, everything circles the drain.
This type of problem is far easier to fix via brute force stripping out of individual .js files than trying to use tools to diagnose.
It ain't pretty + single .js file stripping is the last ditch approach that always works.
ASKER
Thank you for your help.
I guess I have some work to do.
I guess I have some work to do.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.