Take the 2-minute tour ×
Ask Different is a question and answer site for power users of Apple hardware and software. It's 100% free, no registration required.

For the past few months, attempting to close Safari normally (Command-Q) quickly closes open browser windows, but takes forever (~10+ min) to fully close, if it closes at all.

A look at the Activity monitor shows that the sub-process Safari Webpage Preview Fetcher churns away, often at high CPU usage (~50%), for a few minutes, but then it and all other Safari related processes drop to zero CPU, but Safari still will not go away. I am only loading the default set of top sites, i.e. have not specified any particular top sites since the last time I reset Safari a few weeks ago.

This behavior existed for me under Snow Leopard, and has sadly continued after a recent upgrade to Lion. I am now running OSX 10.7.3 with Safari 5.1.3

I can of course force quit, but it would be great to be able to quit normally. I would consider stopping Top Sites all together as is described in another post, but would rather decouple that option from simply getting Safari to quit normally. I am also not sure if the top site disable even works in Lion (and am too new to comment on that thread).

How can I get Safari to close normally?

Update: this behavior is somewhat intermittent. I will try to update this question as I identify possible/reliable triggers. For now it seems opening Safari and running simple Google search doe not cause a slow close.

share|improve this question
    
Just curious, how long does command-option-Q take? –  Lucas Derraugh Feb 28 '12 at 5:42
    
Interesting thought. I just looked up command-option-Q to find that it causes a close without remembering last open windows (new on Lion?). I'll do some experimenting. –  Bryan P Feb 28 '12 at 18:56

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.