Not sure if this is the right forum to ask this question. The computer in question is a Mac Book Pro (10.9.5, aka Mavericks).
There is a site that in Chrome that repeatedly comes up with its "Aw, Snap" page. It's really bothering my co-workers that it's loading up fine in other browsers but not in Chrome repeatedly.
So, I've been trying to figure out the answer. I came across the issue of dns cache maybe?
Since the dns command is different based on OS version, I've tried dscacheutil -flushcache;sudo killall -HUP mDNSResponder
to no avail.
Wanted to see if it was working, so tried:
sudo discoveryutil mdnsflushcache
sudo discoveryutil udnsflushcaches
And all I get from those are:
sudo discoveryutil mdnsflushcache
How do I make my dns flush work, and how will I know it worked? And could there be any particular reason why a site won't repeatedly load up in Chrome unless you hit refresh multiple times?
EDIT
Editing to add that I've literally done everything under the sun on Chrome, ie, clear its cache, remove cookies, and reset it repeatedly.
And still the site repeatedly comes up with its "Aw, Snap" page.
discoveryutil
...killall: unknown signal flushcache,; valid signals: HUP INT QUIT ILL TRAP ABRT EMT FPE KILL BUS SEGV SYS PIPE ALRM TERM URG STOP TSTP CONT CHLD TTIN TTOU IO XCPU XFSZ VTALRM PROF WINCH INFO USR1 USR2
sudo killall -INFO mDNSResponder
creates about 300 lines of output in the system.log file. Use Console.app to open this one! There is a space between -INFO or -HUP and mDNSResponder!Console.app
, you meant terminal, right?