Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Solve an apparent 'stuck Safari' crash without losing work Web Browsers
Yes, I know, if you use haxies you get what you deserve. But to this day, Spotlight, enhanced custom keystrokes and all, and in spite of my overall hatred for the mouse versus a good keystroke combo, there are just a ton of things I find easier to do with a right-click and Contextual Menu action when I am in certain work (or leisure) modes, especially Web research and just plain surfing. But the price is getting higher.

Summary of this hint: I was having a spinning beacbhall hang issue in Safari. After some work, I figured out that it was caused by FruitMenu's contextual menu support. Temporarily disabling the contextual menu support -- without quitting or logging out -- instantly ended the Safari hang-up and I was able to start using it again without losing any work.

Read on if you'd like more background on the Safari problems I was having, and how I diagnosed and solved them...

Background: So since around 10.5.6, and the later versions of Safari 3, I started having frequent spinning beachballs of death (SBOD), and was having to force-quit Safari more often than I'd like. Even with Open all Tabs from Last Session to prevent the agony of trying to search through a week of History and bookmarks for what you had left open waiting to read, I would lose window placement, shading, position etc. Also, having to reload up to 100 tabs with previously-placed data for comparison shopping and reading and the like, getting it all back to where I had it totally sucked beans.

Safari 4 has been less-frequent in lock-ups, but the lock-ups were coming harder (if that makes any sense). In other words, whereas in Safari 3.x the jam would occasionally clear if I got up to get a drink or attend another task long enough to wait it out, Safari 4 stayed jammed up even if I went to lunch and back.

Finally, just tonight, my poor addled brain finally noted that the freezes were not very long after having accessed Contextual Menus for some thing or another. Also, I've been having incorrect display of one of Fruit Menu's nicer features, the display and sub-menu access to all local volumes, including mounted DMGs (very handy when you're downloading lots of DMGs and don't want to drop into Finder to access).

Well, this time when the SBOD hit me during an exceptionally long forum post creation, one that I had not copied to clipboard in a while for safety, and I was determined to save my unsaved text -- at least ten full paragraphs (more than twice the length of this overly-long hint).

In Terminal, I ran top -ocpu, which showed flashes of Unsanity-related activity. But it always did and always will; Application Enhancer is CPU-intensive and moreover incessant, like a swarm of gnats at a picnic by the lake. But make the picnic big enough with enough people (Mac Pro Quad), and you hardly notice them, and the food is so good that you will tolerate the gnats for the fish they attract. After a little top and a little ps -aux | grep to confirm, it became as simple as going into the Fruit Menu System Preferences panel, disabling Contextual Menu support, and hitting 'Apply'.

Boom, Safari came back to life instantly. My post was saved. As was my own unsanity. I turned the support back on, did a few more right-clicks inside a text entry form, and, whap!, Safari locked up. Turned it off, Safari is back. Obsessed with my discovery, I set out to reproduce, and reproduce I did.

This happens most often when entering text into a submit form, or doing text selections then something like Search in Google, and is triggered most often by spell check. The thing is that it takes several seconds after you've completed the contextual menu action for the lock-up to occur, so it was not an obvious vector to explore.

This is probably the cause for some freezes and outright crashes in other apps when I use the Contextual Menus there, too. I plan to submit a report to Unsanity (they really are pretty responsive developers), and see how much I can help them help me continue to love using their products.

I hope this helps someone else; just toggle various haxie features off, and you don't have to force-quit, quit, or even log out any more to resolve.
    •    
  • Currently 2.27 / 5
  You rated: 3 / 5 (11 votes cast)
 
[10,459 views]  

Solve an apparent 'stuck Safari' crash without losing work | 7 comments | Create New Account
Click here to return to the 'Solve an apparent 'stuck Safari' crash without losing work' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Solve an apparent 'stuck Safari' crash without losing work
Authored by: slswift on Jun 29, '09 08:07:38AM

Hmmm.... Just last week, Safari 4 crashed hard several times while I was working in text entry boxes. Couldn't think of a cause for it at the time. I don't have Fruit Menu installed, but I do have Window Shade installed.

So for the time being, I've added Safari to the Master Exclude list of Application Enhancer. Now to see if Safari seems more stable.

Thanks for working through the issue. Hopefully, mine is related.



[ Reply to This | # ]
Solve an apparent 'stuck Safari' crash without losing work
Authored by: Fairly on Jun 29, '09 08:33:41AM
Who needs haxies?
http://bit.ly/2Cit3y

[ Reply to This | # ]
Solve an apparent 'stuck Safari' crash without losing work
Authored by: barefootguru on Jun 29, '09 01:39:35PM
Exactly. Programs which modify running applications or the system are more trouble than they're worth. Apple bins all crash reports which include haxies and BareBones has been similarly scathing of them. Classic Menu also brings back the Apple menu but without a nasty hack. http://www.sigsoftware.com/classicmenu/

[ Reply to This | # ]
Solve an apparent 'stuck Safari' crash without losing work
Authored by: Frederico on Jun 29, '09 04:05:15PM

Heh.

I got a little wordy that night; manic high combined with multiple bug troubleshooting and scripting around iPhone deficiencies left me buzzing on the keys for too long.

Poor Rob had to not only read my ramble, but edit it into something you guys would actually read.

He cut out the parts where I said, "I dutifully submit my Apple Bug Reports, but I read somewhere that there bug tracking system automatically ignores any report when haxies are detected in the System Config. Doesn't surprise me, if true.

"It will be a long time before I can wean myself off haxies; especially FruitMenu and Windowshade. But I hope this helps someone else; just toggle various haxie features, and you don't have to force-quit, quit, or even log out anymore to resolve. God Bless *NIX. And long live the haxie; their usefulness outweighs their occasional gnatiness."

And please don't forget that I opened with, "Yes, I know, if you use haxies you get what you deserve."

I've looked at the link above many times over the past whatever period, and it simply doesn't replace all the haxies I'm using; nor does it even address the stated benefits in this post for specific CM functions. Even if it did the one, once you haxie in for a penny to get the others, you my as well haxie in a pound and enjoy what you can.

So, as stated, we who use them get what we deserve. And we try to support ourselves by passing along tips to deal with certain problems until the developers catch up.

HTH

Rico



[ Reply to This | # ]
Solve an apparent 'stuck Safari' crash without losing work
Authored by: RobLewis on Jun 29, '09 08:33:52AM

I was so hoping this might be related to a problem I've been having:
Ever since the first beta of Safari 4, the "Command-click to open in a new tab" function has been broken (under OS X Server 10.4.11). I have to Ctrl-click to get the contextual menu, then select "Open link in a new tab". Annoying!

But disabling App Enhancer for Safari didn't change anything. Bummer.



[ Reply to This | # ]
SPOD, please
Authored by: SuperCrisp on Jun 29, '09 03:55:05PM
Hey, let's stick with the accepted and more easily pronounced acronym, SPOD , for Spinning Pinwheel Of Death. And while you're at it, you can stay off my lawn!

[ Reply to This | # ]
Solve an apparent 'stuck Safari' crash without losing work
Authored by: r2242 on Jun 30, '09 08:30:09PM

Give FinderPop a look. I run as few add-ons as possible, but couldn't live without FinderPop. GREAT add-on!



[ Reply to This | # ]