Click here to Skip to main content
15,888,454 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Does anyone have any suggestions on the aw snap error in chrome?
I have tried all the usual solutions (Virus program checked, chrome profile removed, spyware search, ...)

It only happens on my website (jsp) and after a certain amount of time of inactivity (I have a gut feeling it might be session end, but since it never reposts, this shouldn't be the case?)
No issues on other browsers.

I'm using Windows 7 64bit, Chrome 26.0.1410.43 m.

my next idea is to check up on the javascript stuff...

thanks.

[UPDATE]
The root cause is that chrome appears to have a memory leak (IE does not have this problem)
The weird thing is that memory remains constant until it starts rising after exactly 15 minutes and almost doubles in memory each minute. when it is higher than 1 500 0000 K the "Aw snap" error appears.

Found it after someone mentioned memory leak.

My guess is this is related to either:
1. JQuery
2. JQPlot

(My only timed event in my own javascript was disabled for this test)

I can now search for a more detailed root cause and see for a fix or workaround. Any tips or known issues are always welcome :-)
[/UPDATE]
Posted
Updated 28-Mar-13 2:17am
v2
Comments
Sergey Alexandrovich Kryukov 27-Mar-13 10:38am    
Not enough information. Can you provide code sample and steps to reproduce the problem?
—SA
V. 27-Mar-13 12:10pm    
Hi Sergey. That would be very difficult. I don´t know how to reproduce it. I use my website and there is no problem. If I don´t attend it for a while, chrome suddenly shows the aw snap page. I put breakpoints in the server code, but it´s not getting there. Apparently it looks like a chrome issue, but I would like to find the root cause. Giving code, sure, but I would need to know what part causes the issue, which I don´t know, yet.
Sergey Alexandrovich Kryukov 27-Mar-13 13:31pm    
Then it would be hard to suggest anything... There is no such thing as miracle.
—SA
V. 27-Mar-13 14:07pm    
I know.
Sergey Alexandrovich Kryukov 27-Mar-13 14:15pm    
:-)

1 solution

I solved it like this:
JavaScript
var isChrome = (window.chrome != null ? true : false);
if(isChrome){
    var current = new Date();
    var timedifference = current.getTime() - autorefreshtimeoutcounter.getTime();
    if(timedifference >= (15*60000)){
       autorefreshtimeoutcounter = new Date();
       //refresh here by doing a postback
    }									//end if
}									//end if


I'm always open for better suggestions as I see this as a workaround, rather than a real solution.
Call me lazy, but I didn't want to start debugging and searching both JQuery and JQPlot libraries for a memory leak.
 
Share this answer
 
Comments
ZurdoDev 28-Mar-13 9:33am    
yuck. Hope that works.
V. 28-Mar-13 9:36am    
still running without a flaw. I'm not 100% happy with it either, but as I said, I'n not going to start debugging the libraries.
Nowfal Sharafudeen 1-Mar-16 7:37am    
In which part you added this code block? In Page OnLoad event or any where else?
V. 1-Mar-16 8:30am    
This has nothing to do with server side events. this is pure javascript code. The page was completely finished. Besides, this question is almost 3 years old, although the code was cleaned up in the meantime, the error never returned.
Nowfal Sharafudeen 1-Mar-16 8:39am    
I asked this question because, I am also facing this issue still in Google chrome. Can you suggest any solution? :)

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900