2.02 Killed Safari

When I launch Safari, after installing the 2.02 update, the screen goes black. It does not matter if I am on cellular or WiFi - black screen every time. This is ridiculous. ANybody else with this update experiencing this and find a solution?

Found my own solution: reset all settings on iPhone.

Similar Messages

Killing "Safari Web Content"

Hi,
I recently upgraded to Safari 6.0.
In the previous version of Safari (whatever the latest 5.x was), when the process "Safari Web Content" got too large (memory-wise) I could force-kill it using Activity Monitor. The behavior when that happened was that most (if not all) of the Safari Web Content memory would be freed, and all of the open tabs on Safari would be reloaded. This was very good behavior, IMO, because it allowed me to retrieve some memory without losing any content (other that now being unable to go back.)
In Safari 6.0, when Safari Web Content is killed, the entire Safari process is killed, and you have to start from scratch.
Was this an accidental feature (aka a bug) in Safari 5.x, or was this change intentional? Is there any way to free up memory in Safari 6.0 without killing the whole thing? Safari 6.0 seems to continue the trend of Safari being a real memory hog (apparently much worse than Google Chrome), and the behavior of 5.x was very useful in that regard.
Thanks,
Geoff

Clear the history...
From the Safari menu bar click Safari > Reset Safari
Select Clear History
Deselect the other boxes then click Reset.
Quit then relaunch Safari to test.

Help! I killed Safari on my mac!

Ok so I recently I discovered there were add-ons available for Safari and I installed this one called Saft
but I didn't like it because it was just a demo and a message kept popping up telling me to register it, so I decided to unistall it, I used AppCleaner to delete it, after that, I opened safari and the annoying pop ups were still there as well as all the stuff from the application in other words it didn't go away from Safari, so I went ahead and deleted safari, and reinstalled it again, but now it freezes upon opening it, it doesnt load any pages, nothing! it just freezes.
How can I fix this problem?

Try finding any stray bits of Saft and deleting them. Close Safari first.
You fill find them in one or either of these folders:
Home/Library/Input Managers
Hard Disk/library/Input Managers
Hard Disk/Library/Application Support

Flash is killing Safari, which is leaking memory ...

I just saw in Activity Monitor that the Flash plugin is using 147% of the CPU, with one Flash movie playing in one of 12 open Tabs
And Safari seems to leak memory as well, after a day or two it easily can use up to 3GB(!) of RAM.
I am now quitting Safari routinely every 2 to 3 hours to get the CPU usage down and free RAM for other stuff, but I don't think this method makes for a great user experience.

Hi,
Use ClickToFlash... that way you have control of Flash content.
http://clicktoflash.com/
Carolyn

Adobe Updater kills Safari

The Adobe updater cranked up about an hour ago and wanted to install an After Effects patch. I was requested to quit Safari to do it. I did. The patch installed OK. Safari now cannot find any URL. Enter any URL and only blank shows.
Suggestions?
Thanks, Hal

Console shows:
1/30/08 3:14:02 PM Safari[191] * WebKit discarded an uncaught exception in the webView:resource:willSendRequest:redirectResponse:fromDataSource: delegate: <NSInvalidArgumentException> 0x12a00380 [RKSortedRegexCollection sortedRegexCollectionForCollection:library:options:error:]: (formatString is NULL)

IOS 5 Safari JavaScript execution exceeded timeout

I am working on a mobile web app that is primarily self-contained and communicated with the server only when necessary. Currently, the libraries being used are:
- jQuery 1.6.4
- jQuery UI 1.8.3
- Modified/patched version of jQTouch
Up until the release of iOS 5 we were also using touchscroll.js but it is no longer needed since Safari now supports position: fixed and native scrolling.
Since the release of iOS 5, seemingly at random, this exception is raised:
    JavaScript: Error undefined JavaScript execution exceeded timeout
Once it is raised, no JS code that runs for more than a *very* short period of time (say 1ms) will be executed by Safari. Refreshing the page, going to a new page, or going to a new domain has no effect. Any and all JS code, even something as simple as
    for(var i = 0; i < 30; i++) ;
will not be executed by the browser without the exception being raised. The only way around this is to force kill Safari and restart it. I suppose it is also possible to wrap any remotely "heavy duty" code in the application in a window.setTimeout(..., 1) or take advantage of Web Workers for everything but UI updates but that doesn't seem like a very good solution as the application is fairly large and it would require a substantial rewrite.
Has anyone encountered this issue before? How would you go about debugging something like this as it isn't any single piece of code that seems to put Safari into this broken state and it can happen seemingly at random?
I tried to figure out what the timeout of the JS engine is in mobile Safari by doing the following:
    var start, end;
    start = new Date();
    try {
       while(true);
    } catch (ex) {
      alert('test');
    end = new Date();
    console.log(Number(end) - Number(start) + 'ms');
Unfortunately it seems this timeout exception isn't a JS exception so it cannot be caught in a try/catch block; however, it appears the max timeout period is in the realm of several seconds. None of the code in our app locks the browser/JS engine for that long (as it would provide a terrible UX) and most if not all of it probably has a sub 300ms execution time (including anything that's "heavy duty").

illvminatvs wrote:
Sometimes even simple DOM queries in jQuery like $('.foo') would trigger this behavior.
There is nothing simple about jQuery. I'm pretty confident I could create a page where such a selector would bring any desktop browser to its knees.
Moreover, this issue did not exist in iOS 4 and only manifested itself in iOS 5 and IIRC only occured on iPad 2 devices and not the original iPad.
I highly doubt that.
So call it what you will. I'll call it a bug.
What I'll do is put on my overalls, grab my cane, and tell you how it was in my day.
Back in my day, every operating system had bugs. Every application running on them had bugs. You know what we did? Blame the vendor? Yep. Filed a bug report? Sure. Sit on our hands? Never! You know what we did? We "worked around it". There was no internet where someone would post just the lines of code we needed. There were no example apps. There was no open source. Somehow, we still got it working.
Just suppose, for the sake of argument, that you are absolutely correct. This is a bug the Apple introduced in iOS 5 and it breaks your app. Will Apple release a fix for it next month? Unlikely. Next quarter? Maybe, maybe not. 2015? My oldest Apple bug report is dated "04-Apr-2008 06:39 PM".
It is an imperfect, competitive world. If you don't want to work around the bugs, all that does is give that opportunity to someone else.

Safari Web Content consuming all my memory

I'm having a problem with Safari Web Content.
I've jst re-loaded Mountain Lion in a brute forcve attempt to resolve my issue, but it's still occurring.
The issue is: with very little running, if I run Safari and bounce around a few websites, I can easily consume all my memory. I end up with this:
As you see, Active memory is too high (before this test I had Mail open, and Avtive memory was about 2GBm what you might expect normally).
Actibve memory had actually peaked at about 3/4 of the total, but then some must have got swapped out to Inactive.....giving us the picture above.
But look at the Real Mem occupied by Safai Web Content! That can't be right, surely.
Nevertheless, I'm led to believe that OSX's memory management algorithm's will swap out Inactive for Free when it is required....well, this isn't happening. I saw Free memory down to 7MB at one point, not a typo. Everything grinds to a halt.
If I am patient, and try to Quit Safari, I end up back here:
Clearly showing that if I manage to kill Safari, the memory gets freed up again.
I understand why OSX wants to handle memory with the Inactive concept - "you've just closed Word, but maybe you'll open it again in the next ten minutes so we'll leave it in memory, inactive, so when you try and open it, it will open really quickly". Right now, I'd rather turn that freature off and have memory behave more primitively and take the hit on re-opening.
As I mentioned, I reloaded OSX Mountain Lion and the problem persists. When you re-load or upgrade your OS, there are many configuration settings (desktop, mail, safari) that are kept so that the upgrade looks seamless; clearly whatever is corrupting me here has been kept also. For that reason I'm loathe to go to Mavericks, because I presume the same corruption would exist (and also I hear Mavericks is still a bit shaky with the native Mail app).
What config type files should I look to safely delete and have the OS rebuild? Any ideas?

OK, so I tried a Safe Boot. It wired 5GB of memory, and for a while I thought what was left would behave itself, but within about 10 minutes I consumed everything again.
Here's the before:
And here's 10 minutes later, after bouncing around a few websites:
I also tried firing up Safari, going to Facebook, and letting it sit for a while. No effect.
So, the problem occurs when visiting multiple sites - memory isn't getting released properly.
I think I'm left with a move to Mavericks.

Just downloaded Lion to my iMac, cant exit Safari since.

Lion is working good so far but vant seem to exit Safari, wondering if this is normal as my first reaction was a virus holding my connection.

Don't turn off the computer. CTRL- or RIGHT-click on Safari's Dock icon and select Force Quit from the context menu. If that doesn't kill Safari then:
Open Activity Monitor in the Utilities folder. Select All Processes from the Processes dropdown menu. Click twice on the CPU% column header to display in descending order. Select Safari's item in the processes list then click on the Quit icon in the toolbar. Click on the Force Quit button.
Navigate in the Finder to the /Home/Library/Caches/ folder and delete the two folders with com.apple.safari in their names. Re-open Safari and see if that now fixes the problem.

Safari runaway heating followed by beachball; force quit necessary

Safari 3.2.1 has become unusable for me as of today. A few minutes after I launch it, I hear the fans start to rev up, and I can see the temperature climbing. Quit doesn't work, only force quit. Knowing how my MacBook Pro is subject to runaway heating every so often (anyone have an idea why?), I am sure that if I didn't hurry to force quit at 80 deg C, it would keep on climbing to 110 before causing a shutdown of the system. It started as a problem with one particular site, but now it doesn't matter where I am. I tried reinstalling Safari, but it had no effect. Am I the only one to have enountered this?

I can confirm having exactly the same problem, which also started on March 30th.
I've done a 'Safari reset" for all the reset-items except for usernames+passwords and for autofill. It doesn't make any difference. Even if I only start Safari without accessing any sites (I have my Safari-homepage defined as None) then after about a minute Safari (vs 3.2.1) starts cannibalizing on CPU-time (as shown by the Activity Monitor utility), shooting up to 90-100% - and staying there! This renders Safari completely useless, as it blocks out other apps from using any meaningful part of total cpu-time. The only way to stop this is to kill Safari using Quit Process in the Activity Monitor. Firefox and Opera, which I both have also installed, do not show any similar problem whatsoever and operate completely normal. I have not installed any new software before this weird Safari behaviour started and Software Update reports that all my software is up to date (OSX 10.5.6). Something is somehow dead wrong within Safari.

Safari 3 - Dual-monitor problem.

I've just installed Safari on Windows Vista Business. When I move the windows on my secondary monitor, a soon as I try to maximize it, it desappear. The program is still in my taskbar, but I can't minimize or anything. The options are greyed-out. The only thing I can do is to kill Safari and restart it.
Is anyone has experiencing the same problem ?
DELL Inspiron 6000 Windows Vista

I've just tested Safari on a multihead Windows XP system and suffered the same problem. Display 1 is laptop primary display, and display 2 is configured to the left of laptop display and is an external LCD.
If you right click on the Safari button in the TaskBar and select Move, the cursor appears at the top left hand corner of display 2, and I think I can see a one pixel edge down the left hand side of display 2 that may be the Safari window. It starts a few pixels down from the top left and appears to be black 1px wide, and when you close Safari it disappears.
HP Compaq nx9110 Windows XP Pro

Safari v4.0.5 for WinXP freezes at 71% of the test of Sputnik

Safari v4.0.5 for WinXP freezes at 71% of the test of http://sputnik.googlelabs.com

yes. it slows down at 61% for me and I have to hit a pop-up prompt to continue.
Hmmm. I didn't get that the first time around, but when I tried to resume the test (after having to kill Safari via Task manager), I'd be resumed at 60% and started to get the "slow script" pop-ups.
It's pretty much "slow script" pop-ups all the way from 60% onwards with IE 8. I think that particular IE 8 browser window has died now. Can't open it, and my CPU is lurking at about 50%. (Usually just one of my processors gets maxed when a process/service/application goes into a tizzy.)
It's probably worth submitting a bug report to Apple about the Sputnik hang. I can't get "Help > report bugs to Apple" to work while Safari is hanging at the 71% mark. But if you go to the Sputnik page (in Safari) and do that prior to running the test, and describe the problem in the comments field, I think the engineers should be able to work out how to replicate it.

Safari pinwheels and freezes the entire system.

Safari pinwheels and freezes the entire system.
I've read numerous threads with this Safari pinwheeling theme, but none of the posted solutions I've found work for me.
The problem:
Safari will almost always on opening, and frequently when filling in forms on websites, start pinwheeling. The whole system then slows down, and then eventually freezes. Even the dock bar freezes. When this happens, I can't even bring up the Force Quit bar. The freezing will often last several minutes, then all of a sudden, all my various previously ignored mouse and key clicks cycle through. When Force Quit finally starts, then everything freezes again. Eventually, Force Quit will show Safari as not responding, and once in a while the system then will start responding, but usually I have to kill Safari.
The problem subsided a little bit on the opening the application problem when I switched my start page from Apple.com to Google.com, thinking that maybe it was just too much graphics crap coming in on the Apple site.
The problem happens on both my Airport and cell modem network connections.
I may have seen this behavior once with Firefox, but haven't been able to reproduce it.
Generally I only have a few things running: Excel, Messenger, Safari.
Things I've tried to fix this:
Reset Safari
Clear Safari Cache
Delete Safari folder in the system cache folder
Went into the Energy Saver in Preferences and unchecked, "put disk to sleep when not in use" for both the battery and power adpater settings
Limit number of tabs open
I'd try restarting Safari occasionally, but the problem usually happens on opening.
I've emptied the trash, and made sure there is ample open disk space (10gb right now).
Resolved duplicate fonts.
I have no third party apps to affect Safari or networking.
I've reset the machine by unplugging it and holding the power button.
My computer is a MacBookPro 15" with all the latest software and firmware updates and 2gb RAM. This has become so frustrating, it's been very tempting to just throw the laptop at the wall and go back to my Windows laptop...

I'd say the bad blocks were behind the problems you were seeing. Their existence points to either a defective HD, or directory corruption. The latter usually can be repaired by using a Utility such as Disk Warrior, or as you did, reformatting the drive.
Best approach to minimizing directory problems is to do routine maintenance twice a month. Have a look at this MacWorld article for suggestions.
For routine maintenance I use OnyX. There is no charge for the software, but I believe the developer asks for a donation.
It's very easy to use. I run it twice a month. Once it is installed, you would double click on the OnyX icon in your application folder (or drag an icon to your dock for quick access) to open the application. After entering your administrator password, you would select "automation". The panel looks like this:
Select the same items I have checked. The program takes about 5 to 10 minutes to run. Leave your computer alone, that is, don't use it for anything else until OnyX is finished. Once complete, restart the computer and you're good to go.
Lastly, the most effective maintenance is having a full backup of your system on an external hard drive. All machines fail eventually, despite the best maintenance. If you had a hard drive failure without any backup, then you would lose all your information, including documents, images, songs, etc. Not a pretty picture.
For your system, you would purchase either a USB or Firewire Drive for your new Intel Machine. The key here is creating a "clone" backup on the drive, which you back up regularly, or at least once a week. For the backup process I use SuperDuper. Very easy to use. The initial backup takes about 1 to 2 hours. Subsequent backups take 5 to 10 minutes. Total $$$ investment can be anywhere between $100 - $250 depending on the size of your Hard Drive.
Post back if you need any other information relative to your questions here.

Safari hogging CPU and won't run

Sorry for posting here, but I couldn't find the Safar for windows section.
I run WinXP (fully up to date), with 2Gb RAM, (with one 1Gb on my gfx card), 1.8Ghz processor
Having updated to the latest Safari I'm finding that it hogs CPU so much so that when I select a page from the top sites screen my PC locks up and I have to use the application manager to kill Safari.
The same thing happens when I try to go to a website just by typing into the address bar.
Anyone having similar issues, or able to help me out as to how to fix it?
Thanks

Try turning off plug-ins, java, javascript
Empty history, caches, etc or go to where XP would store the application temp files, in Windows Vista/7 that is AppData\Local and \Roaming
Disable or turn off extensions, 3rd party can break with any Safari update
make sure you have current Flash etc
I'd stick to Firefox or something - use NoScript, HTTPS Everywhere, FlashBlock, etc.

Keyboard slow to appear in Safari

I have a brand-new IPad 3. I'm having an issue with Safari and the keyboard. If I click on any field in any website, it comes up immediately. It also appears immediately in any other app.
But if I click on the URL or search fields at the top of the browser, the keyboard takes 20-25 seconds to appear.
I've tried killing Safari from the multitask bar, also full power-off as suggested from other threads. No change.
Any other ideas?

you may have simply run the available memory down. double tap the home ket to see th recently used app task bar. touch and hold any of the icons until they jiggle, then close them off by touching the minus sign. Then reboot the pad by pressing and holding both the sleep and home buttons until the apple logo appears. ignore the red slider.
If this solves if for you, remember the steps. and do this from time to time as needed.

Mac AppStore crashing when Flickr opened in Safari...

Hi;
I had a strange problem today. Some updates emerged in AppStore so I decided to switch to AppStore and update them. Nothing serious. When I clicked update AppStore srashed with JavaScript error causing memory problems. I restarted AppStore several times but no help. Then I closed Safari with Flickr page opened and try to update it went fine. I think that both of them use same engine. Flickr is using Javascript a lot I think so it can be connected. I will try to reproduce problem when another update will be available or when I will install new application. So far it seems problem can be fixed by closing Safari and Flickr page. Anybody experienced something like constantly crashing application store without apparent reason?
Marian

I did crash again hard way. Safari stop responding first and then I had been logged off. When I log in back again system (desktop) came back up again till Safari was opened. Then it stoped responding and as AppStore came up it crashed immediately. I was not able to access dock and switch applications. I used Command-Space combination to bring up spotlight and run Monitor. I killed Safari which was not responsive but I was not able to make Dock working. Something went really bad this time. I decided to reboot after that everything started to work fine. Crash report follows:
Process:         App Store [23701]
Path:            /Applications/App Store.app/Contents/MacOS/App Store
Identifier:      com.apple.appstore
Version:         1.2.2 (129.15)
Build Info:      Firenze-129015000000000~6
Code Type:       X86-64 (Native)
Parent Process: launchd [138]
User ID:         501
Date/Time:       2013-06-26 23:15:25.664 +0200
OS Version:      Mac OS X 10.8.4 (12E55)
Report Version: 10
Crashed Thread: 33 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
*** Unable to set attributes on mach port. (268451842) ***
Thread 0:: Dispatch queue: com.apple.main-thread
0   com.apple.WebCore                   0x00007fff8f4f9d7f WebCore::RenderLayer::isSelfPaintingLayer() const + 15
1   com.apple.WebCore                   0x00007fff8f4f7385 WebCore::RenderBoxModelObject::styleWillChange(WebCore::StyleDifference, WebCore::RenderStyle const*) + 85
2   com.apple.WebCore                   0x00007fff8f4f6a75 WebCore::RenderObject::setStyle(***::PassRefPtr<WebCore::RenderStyle>) + 101
3   com.apple.WebCore                   0x00007fff8f5176d9 WebCore::RenderObject::setAnimatableStyle(***::PassRefPtr<WebCore::RenderStyle> ) + 153
4   com.apple.WebCore                   0x00007fff8f524d16 WebCore::Node::setRenderStyle(***::PassRefPtr<WebCore::RenderStyle>) + 38
5   com.apple.WebCore                   0x00007fff8f524606 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 854
6   com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
7   com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
8   com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
9   com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
10 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
11 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
12 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
13 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
14 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
15 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
16 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
17 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
18 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
19 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
20 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
21 com.apple.WebCore                   0x00007fff8f5249a2 WebCore::Element::recalcStyle(WebCore::Node::StyleChange) + 1778
22 com.apple.WebCore                   0x00007fff8f4f405f WebCore::Document::recalcStyle(WebCore::Node::StyleChange) + 559
23 com.apple.WebCore                   0x00007fff8f51e0c3 WebCore::Document::updateStyleIfNeeded() + 67
24 com.apple.WebCore                   0x00007fff8f529cb7 WebCore::Document::updateLayout() + 55

2.02 Killed Safari

Similar Messages

Maybe you are looking for