Currently Being ModeratedJan 15, 2013 8:34 PM (in response to muggle95)
It doesn't sound like a Safari problem to me. It sounds more like an ISP,or DNS snafu. Have you called your ISP? Has anyone changed the Network settings? Are you the Administrator of your Mac Accounts? Has anyone put on parental controls, changed the firewall settings, or have you put on any new "Security" internet app on?
Currently Being ModeratedJan 17, 2013 11:22 PM (in response to ~Bee)
Bee: Those are all good questions.
As a college student with a campus-wide network, I have no clue if anything's been changed, though we usually get emails about planned outages for maintainence. I also wouldn't know who to call. But as I said, my other browsers worked just fine (I specifically tried Chrome) so I'm pretty sure the trouble wasn't in the network.
The account with my name is an administrator, and I keep a second accont around, called "Admin" for when programs die and are harder to troubleshoot, mainly to figure out if I've just done something stupid and messed up my account rather than the whole program acting up. I didn't use that, because I tried another browser first. If that hadn't worked, I would have rebooted and seen if that helped. If that didn't help, then I would have experimented with the Admin account. I probably would have suspected the network at that point, and borrowed a friend's computer to test it.
Anyway, those two are the only accounts currently on the computer, and both are password protected. No one else has access to it, (even my roommate won't brave the disaster area that is my desk) and I didn't change any settings recently. I don't think I've downloaded anything in the past week or more. The last thing I installed was months ago. (That's the long version of "no new security apps")
That aside, I'm still not sure exactly what the problem was, but I think it was exacerbated by my laptop's heat issues. Because in the morning, Safari worked normally again. At that point, my computer had been asleep all night and had cooled down. If it had been off I would probably conclude that clearing the RAM helped, because it feels like memory is more closely related to how applications behave than heat is, but it was asleep and held onto all of my session data.
The issue is resolved as of ~16 hours after the fact. Is there a way to mark it as such?
I mean, I wouldn't mind continued discussion, in case that happens again, but it hasn't happened since. My computer has reacted much more predictably to heat and simply crashed. I think I like that better: I know what the problem is and how to fix it.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points