Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Every time I open up Safari on bootcamp, it flashes a message Safari has encountered a problem and needs to close. but this is patently untrue. If I ignore the message, as I am doing now, the browser functions perfectly fine, but if I Send/Don't Send the error report, it just quits.

Why is Safari lying to me? I would attribute it to laziness were Safari a person, but it is clearly a computer program running in Windows XP on Bootcamp in a mid-2009 unibody MBP.

share|improve this question
It encounters a problem, this doesn't mean it has crashed. The problem might result in side-effects if you use the browser prolonged, or it may not because an extension has crashed. – Tom Wijsman Aug 15 '10 at 23:17
That title is almost asking for downvotes. But at least it's not as bad as the "Why doe MACOSX suck?" title. – Hello71 Aug 15 '10 at 23:44
What version of Safari? And have you tried reinstalling? – Vervious Aug 15 '10 at 23:59

Perhaps a plugin has crashed in some thread with a plugin and Windows is like "yo that thread owned by Safari has died so Safari is probably screwed up too; you should quit it".

That would be my guess. Go install Chrome. That browser has the same html rendering engine which is called Webkit. Heck, you could probably even sync up bookmarks and extensions with the Chrome in Windows and Chrome on the OS X side thanks to the built in syncer!

share|improve this answer
addendum: the extension sync thing is in the beta version though. – crazysim Aug 16 '10 at 6:35
Since Chrome is crash resistant, you might also be able to locate and isolate the crashing plugin with that as well. – crazysim Aug 16 '10 at 6:35

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .