Cumulus Support

Hi,
Not sure if it's just my latest version Chrome Browser or others see same, but when I leave anyone's (Wilmslow/warehamwx/my own .etc) gauge Page running for a period (variable) they all result eventually in the page not displaying and displaying an Aw-Snap error (something went wrong).
Does not seem to do it in I.E or FireFox.
Any one else noticed this. Oh and apologies if it has been raised before (though my forum search returned nothing on this subject).
Kind regards,

I saw this at work today for the very first time. I thought it was just a fluke. Maybe not....
Nope. It isn't It just did it here at home.

Thanks wi3x,
Glad to know it's not just me.
regards,

Ah, so it's not just me! I've spent a while looking at my browser installation. Sounds like it is a general issue with Chrome 66

Unfortunately it is proving very difficult to get any debug information out of Chrome when an "Aw, snap!" error occurs. I've tried debug logging with --enable-logging --v=1 but not seen anything useful in there. Maybe somebody else can try it?

mcrossley wrote:Ah, so it's not just me! I've spent a while looking at my browser installation. Sounds like it is a general issue with Chrome 66

Unfortunately it is proving very difficult to get any debug information out of Chrome when an "Aw, snap!" error occurs. I've tried debug logging with --enable-logging --v=1 but not seen anything useful in there. Maybe somebody else can try it?

HRVistaWeather wrote:Thanks wi3x,
Glad to know it's not just me.
regards,

Thanks for pointing this out. I saw it for the first time yesterday and didn't really pay attention. I'm not going to waste any time tracking this down and hopefully it will go away. One other point, I did try to run it in an incognito window with the same results so I suspect it is not a cache problem.

Well,
now as of this morning 4/27/18. my gauges run to the full time out limit (2 separate stations). I have mine set for 60 minutes.

I just did a clean install of Chrome Dev (67) and just loaded my gauges page - crashed after about a minute. There is one issue I spotted marked for fix that may help - about crashes in background updates, I'm not holding my breath though.

May be worth enabling crash reporting in Chrome, or going to the "chrome://crashes" page manually reporting the crashes. The more reports they get the more interested they may be in fixing it...

Well, like a fool I upgraded Chrome. I also can't run for more than a minute. Dumb Me.

I'll report it as suggested. All was good before the upgrade.

Hi Mark,
Just another observation : sites using "jquery/3.3.1/jquery.min.js" do not display Graphs on mouse over.
I just tested on my site as well, so reverted to older version I have been running which is "jquery/1.8.2/jquery.min.js".
Kind regards,

HRVistaWeather wrote:Hi Mark,
Just another observation : sites using "jquery/3.3.1/jquery.min.js" do not display Graphs on mouse over.
I just tested on my site as well, so reverted to older version I have been running which is "jquery/1.8.2/jquery.min.js".
Kind regards,

Just tried my test site with a vanilla install (jquery 3.2.1) and changed to 3.3.1 and I get the graphs in the mouse-overs OK. Can you point me to a site that is failing?

I am getting an Aw, Snap! error on the CumulusMX main page page on port :8998 as well

Hi Mark,
With ref to (jquery 3.3.1), no I don't know of any other sites. It only occured on mine when I changed to 3.3.1 , however I noticed your charts don't display (I envisage you have them turned off).

With ref to your (CumulusMX main page page on port :8998) issue, it was not because you had the gauges page open was it.
I find that it Aw-Snaps other open tabs/even other instances of Chrome running.

regards,

My "production" site has popups turned off. I have a test site I use for pretesting releases etc.

The CumulusMX home page has gauges on it, so I guess that is why it is crashing. I only see it affecting the tab that has gauges open.

I've been getting the 'aw snap' error a lot lately with Chrome when I view my MX site (http://xxxxx:8998) using sockets. I haven't tried changing to ajax. It seems to be an issue on the mobile versions of Chrome too (I use Brave, which is a derivative of Chrome) too, but I don't get the 'aw snap' error. It just decides to drop the connection.

I have started getting the Aw Snap error on Cumulus MX (http://localhost:8998/index.html). I am running Chrome on a Mac High Sierra 10.13.4 (17E202). There was an OSX security patch applied today, since when I get the Aw Snap error (might be a coincidence of course). The Cumulus MX page reloads fine every time manually but then 2-3 minutes later it goes Aw Snap again.

Strange because it's been running like a dream for ages.