Problem with Chrome Browser.

[BobW55]

This is NOT a meteotemplate issue.

I started last week to have an issue when viewing my website using Chrome.
http://melvinweather.com/template/indexDesktop.php

Every 60 seconds (give or take a few) it will suddenly give me the AW SNAP message.
If I use any other browser it does not happen, nor does it happen with other web sites.
I have followed Chromes steps to resolve the issue to no avail.
I thought I would ask here in case one of you have run across this problem.

I have updated Chrome to the latest version, I am running Windows 10 Pro.

[LOBWX]

Try this thread.

viewtopic.php?f=47&t=1348&p=6381&hilit=snap#p6381

~Bob~

[John B]

Yes, Bob, I have not solved this apparent compatibility problem. To look at it broadly it seems to be a Chrome idiosyncrasy, as you have discovered by checking your site with various browsers. Unfortunately the majority of visitors to my site use Chrome. However, by increasing my API and plug-in timing to 30-seconds, most visitors will not notice the effect as they do not stay on the home page for long enough (about 6½ minutes) for it to reveal itself. It's now, to me, a minor though annoying problem.

It could, possibly, be a PHP matter, a situation where most browsers accept the coding but Chrome is a little more discerning and invokes some sort of timing criterion that is critical to the code being used. If you are not sure and have not already tried it, take the ssgauges off temporarily your home page and see what happens.

Should you find a solution I would love you to share with the rest of us.

Regards,
John

[BobW55]

John,

Strange part is, it use to function in chrome just fine.
I do not know if chrome introduced some change recently or not.
I'll have a look at the API setting and see what that does.

[WyoDog]

I have been experiencing the same issue. I had enabled CloudFlare caching service on my account. CloudFlare seemed to me to be causing some minor issues, so I disabled it.

Since then, I often receive the 'Aw Snap' error. My page will always reload after that. I, too, followed Google's troubleshooting suggestions, clearing cache, deleting page history, etc. No joy.

I have no solution, just thought I'd throw this out there.

[Dehatter]

I too have been getting this and trying to do some situational research.

in my travels this month I have had the opportunity to use various ISPs. it does happen about 6:28 into a Chrome session with Spectrum, AT&T, Windstream, and Comcast.

it does not happen with Century-Link, or Verizon (wireless tether).

it affects only Chrome and started about 3 weeks ago.

it affects all template webpages I have loaded, not just mine, and when one goes 'Aw Snap' they all do (reguardless of time on the later loaded pages).

Tom

[Dehatter]

I downgraded to Version 65.0.3325.181 (Official Build) (64-bit)

removed the capacity for Chrome to auto update.

works fine.

not much help for my users I'm afraid though, but since its mostly for me anyway....

Tom

[John B]

Yes, Bob, Google brought out a new version of Chrome (v66) - which seems to be the culprit. In my case the nuisance began a day or three or four prior to the 'official' release date. Perhaps those who had auto-update activated, like I did, started receiving the new version slightly earlier.

[Jachym]

I use Chrome 66 and I just left the DEMO opened for like 5 mins without any issues

[Dehatter]

Not sure the demo page is updating.

Has something to do with steel series guages we think.

if you goto my site and wait 7 mins, it will go.

If I update my guages faster than 30 secs it goes much sooner.

I will change it to faster for a few hours/days until you see it happen.

It also kills WU if you have that tab open.

For me this is at
https://www.wunderground.com/personal-w ... H2#history


Tom

[WyoDog]

Chrome Version 66.0.3359.181 (Official Build) (64-bit)

I only see the 'aw snap' failure to load once on the first visit to my page. All pages load correctly after that, including the home page.

Bob, I was unable to duplicate your results.

I would curious if anyone else experienced this at my site. (link in sticker)

[Johnny]

Hi Terry, I opened two browser windows to your MT site, one with Opera and one with Chrome. The Opera page had no problems showing your home page, however the Google Chrome window failed after nine minutes with the Awe Snap warning.

Hi Tom, I opened your Weather Underground page in Chrome and it continued to run without problems for fifteen minutes.

Johnny
Google Chrome Version 66.0.3359.181 (Official Build) (64-bit)

[Dehatter]

try it with my template window open in one tab and the wu page in another. my experience was that both snap at the same time.

[Johnny]

Tried two tabs in Chrome, one with your MT home page and the other on your Weather Underground page, after exactly five minutes your MT page 'Awe Snapped' but your WU page continued to update without a problem.

Johnny

[Dehatter]

Interesting....both snap at the same time for me.

Tom

[Ron]

I'm not the sharpest knife in the drawer (as they say) but this happened to me some months ago, right after I joined and installed MT."Aw snap" and gauges not loading. Also some graphs would not load. I searched everywhere on the Internet looking for the issue. I tried all the solutions I could find. It finally stabilized to the point where everything works (after several updates from Google), but my steel gauges.

I came across a thread, but didn't save the link, where some were discussing "field trials". I don't want to sound like a conspiracy nutjob, but they said that Google tends to "try out" various new components, or tweaks to the browser, on random people. They said to check the system monitor for items that say "field trial". Some of these tests that Google runs in the background, cause problems for different people. At least that is the theory they put forward.

I looked at that time and had 3 or 4 field trial items in the list. Then the problem eventually cleared up, the field trials were down to 1 or two, and after a couple chrome updates things were back to normal. Now things are down the drain again. 2/3 of my page items don't load for me. Apparently, (if this is the cause) it leaves something messed up, until later updates clear it. But that wouldn't explain why FF doesn't work either during this time would it. In the last week, I have noticed the Aw Snaps coming back on various pages. I need to reinstall Firefox and test it.
I have tried clearing Cloud Flare cache, and turning off Cloud Flare for hours, to see if it helped, nope. So Cloud Flare is back on. I restarted my server, no change.

Anyhow, for what it's worth. I just checked since my site won't hardly display items, and I have a TON of these "field trials" listed. This is just 8 that I snagged in the screen shot.
I am running Linux Mint 18.3 Using Chrome and Chromium.

Here is the link to my page, if someone knows for sure that the field trials may not have a legitimate connection, then I'll take my tinfoil hat, back in the drawer. I have no idea what the cause is, but thought I would share what I had observed. http://www.ronscountry.com/weather/temp ... esktop.php

Selection_007.png (67.35 KiB) Viewed 22411 times

[Dehatter]

Of interesting note, the developers preview version of Chrome (Canary) does not Aw Snap.

Version 68.0.3440.5 (Official Build) canary (64-bit)

Tom

[BobW55]

UPDATE:
Tonight I received a chrome update to Version 67.0.3396.79 (Official Build) (64-bit).

So far, 20 minutes and no AW SNAP.

I will cross my fingers it will stay fixed.

For anyone who follows this thread down the line.
THIS IS NOT A METEOTEMPLATE ISSUE
This is something with the Chrome browser

Bob

[Dehatter]

Confirming that Chrome Version 67.0.3396.87 (Official Build) (64-bit) does not Aw Snap!!

Woot!!

[andyk1]

Well I am here to confirm that:

Google Chrome is up to date
Version 67.0.3396.87 (Official Build) (64-bit)

Is awwwwwwwwwwwww snappppppppppping here still.

My main browser for viewing, testing and updating is Firefox which seems to have no issues except java which we know is going away soon anyway. I.E. has issues saving config files but will no long be supported at the end of this month. I hate using MS Edge.