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

Disable BBEdit's 'APE' crash warning Apps
When BBEdit quits unexpectedly, it likes to blindly nag you about disabling Unsanity's Application Enhancer. Of course, the crash may or may not have had anything to do with APE or even BBEdit, and once you've seen this dialog, you certainly don't need to be reminded about it every time you recover from a crash. Unfortunately, there's no option to turn this dialog off, but you can tweak the BBEdit binary so that the APE check will always fail.
  1. First, crack open the terminal and cd into the BBEdit bundle:
    $ cd /Applications/BBEdit.app/Contents/MacOS/

  2. Back up the existing binary:
    $ cp BBEdit BBEdit.bak

  3. Open the binary with vi in ... well, binary mode:
    $ vi -b BBEdit

  4. Search for the string ape:
    /ape [return]

  5. Replace ape with another three letters of your choice. Be sure to use three letters exactly so that you don't shift the offsets of the rest of the binary file:
    xxxixxx

  6. Write and quit:
    [esc] :wq [return]
Now when BBEdit wants to tattle on you for running Application Enhancer, its search for the "com.unsanity.ape" preference file will fail pitifully. You're free to resume your work without BBEdit whining that it's not its fault, leaving you with only the aggravation of having just endured a crash. Let's hope this sets us down the path to lasting peace!
    •    
  • Currently 2.60 / 5
  You rated: 3 / 5 (5 votes cast)
 
[7,460 views]  

Disable BBEdit's 'APE' crash warning | 24 comments | Create New Account
Click here to return to the 'Disable BBEdit's 'APE' crash warning' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Disable BBEdit's 'APE' crash warning
Authored by: jtrott on Jun 13, '05 09:46:25AM

I'd love to turn off the entire whinging after crash dialog. I never have BBEdit crash, it's always due to not waking up from sleep, or a kernel panic or something. I don't want to be told by BBEdit that I crashed - I know I did already!



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: zot72 on Jun 13, '05 10:40:43AM

This is why I had to stop using Mailsmith; I was sick of it telling me (in a really snippy tone) that WindowShade caused problems that I know happened inside a device driver.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: varcos on Jun 13, '05 10:47:33AM

What version of BBEdit are you using that's crashing? I'm using BBEdit 7.1.4 and Windershade, and I've never had that error before.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: Han Solo on Jun 13, '05 11:18:20AM
I use BBEdit regularly and I don't have APE or any "haxies" installed... and its been years since I have experienced a crash with BBEdit (back in some early version of 10.2.x, IIRC).

Connection?

[ Reply to This | # ]

Disable BBEdit's 'APE' crash warning
Authored by: dv8godd on Jun 13, '05 11:46:04AM

Though it would be nice to pin crashes on Unsanity haxies... I just don't see it.

I use BBEdit daily as well AND have APE running with a bunch of Unsanity Haxies... and I too haven't had a BBEdit crash in a long while. Even so, thousands upon thousands of apps run fine with Unsanity haxies in place... if there is an issue with BBEdit and a haxie... it is still most likely at least partially to do with something in BBEdit that isn't quite kosher.

Unsanity's creations are surprisingly stable and smooth... nothing like old MacOS extensions at all... and some are very helpful and not just visual. Folks should avoid equating APE to crashes and general instability when there are so many other, much more likely candidates. OSX is a whole different breed... disabling "extensions" to cure problems and "zapping pram" doesn't really work here.

Even if a haxie brings about a crash more readily (which I doubt), it's more likely than not due to some other problem that won't go away even when the haxie is disabled.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: pub3abn on Jun 13, '05 11:49:04AM

Is there a connection? I use both BBEdit and a couple Unsanity haxies, including Window Shade. They both work perfectly together. I know BBEdit has crashed once or twice over the years, but I wouldn't chalk that up to any particular fault of Unsanity or BBEdit for that matter.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: JKT on Jun 13, '05 11:49:03AM

Good luck getting any user support AT ALL on a product if you have hacked the binary around. This is a really irresponsible hint to post Rob and I can guarantee it that BareBones will NOT appreciate it at all.

---
PB G4, 1.5 GHz, 2x512MB RAM, 128MB VRAM, 80 GB 5400rpm HD, SuperDrive, MacOS X 10.3.9

Visit www.thelandgallery.com for nature-inspired British Art



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: fracai on Jun 13, '05 12:29:56PM

and I'm sure Unsanity doesn't appreciate another developer informing the user that a crash is possibly due to the presence of APE.

I think this is pretty irresponsible on the part of BB in the first place.

---
i am jack's amusing sig file



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: deleted_user18 on Jun 13, '05 12:31:30PM

So then we don't apreciate BBEdit at all. And as long this very useful website is not run by the makes of BBEdit they can post whatever they want.

BTW: I prefer SubEthaEdit - it is Cocoa, it is more modern, it is cooler and it is free.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: wgscott on Jun 13, '05 12:52:06PM

You can get rid of the irritating splash screen that comes up periodically for academic users of SubEthaEdit by editing that binary to replace the two instances of the warning string with an identical number of blank spaces.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: kyngchaos on Jun 13, '05 11:53:01AM

Even easier, no Terminal needed: HexEdit (http://www.ifd.com/product_info.php?products_id=87). Find 'ape' and edit with Overwrite Mode.

Awesome app, but I think the BBEdit authors must have something against Unsanity. Pretty lame to check for existence of other software after a system or application crash and gripe about. Especially when you can't be sure that it was your app that crashed or caused the system crash, or that the other software is the cause. Leave it up to crash reports and system/console logs to figure it out.

And I've been using Unsanity haxies and BBEdit for many years. I've never had problems with BBEdit and APE or haxies. Maybe APE with other software, but those are quickly fixed. APE has nothing to do with BBEdit _not_ crashing, so far.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: Baggins on Jun 13, '05 12:06:34PM

The BBEdit people don't like the idea of code injection, which is what Unsanity does to make their haxies work. BBEdit is being rather childish, IMO.

I'm a huge fan of haxies and have registered copies of nearly all of them. Fruitmenu, Mighty Mouse and Shapeshifter. Especially shapeshifter; it lets me erase that abomination of a menu bar that Apple decided to release with tiger. A 3-d Chrome menu bar with a chalk-drawing Apple logo? Puke.

Fruitmenu lets the Apple menu become what it should have been from the beginning: a customizable global menu, and Mighty Mouse lets me flip the pointer for left-handed use, something Windows users have been able to do since Windows 3.11, but which Apple STILL doesn't allow. Window shade allows me to remap the minimize button to hide the window instead of shrinking a useless icon of it to my already cramped dock.

All of these haxies have run on my system since Jaguar, through upgades and have never given me any system stability problems.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: thornrag on Jun 13, '05 01:07:41PM
I did chat with the BareBones crew some time ago about this matter, and they insisted that the dialog is in response to an inordinate number of support requests from users whose systems had crashed because of APE, rather than BBEdit. The dialog is meant to give users something to try before complaining to BareBones.

The problem is that some of us know precisely why the system crashed, thank you very much. Moreover, we don't need the dialog every time the system crashes. There are any number of reasons why the system might be taken down uncleanly, none of which mean that BBEdit or APE actually crashed. Powerbooks switch off in the bag, power goes out, Finder hangs, you reboot from the command line, testing your product involves simulating crashes... who knows. Meanwhile, BBEdit and APE both seem to be perfectly stable together. So I don't know what this little spitting war is all about.

Basically, I wanted BBEdit to shut up about defending itself, because I never blamed it for the crash.

As for the insinuation that this little hack is a reckless endangerment of the stability of the application, your system, your marriage, and the delicate balance of time and space throughout the universe, I offer the following disclaimer as it should have been included with the original submission:

Editing the BBEdit binary is a reckless endangerment of the stability of the application, your system, your marriage, and the delicate balance of time and space throughout the universe. Doing so violates the integrity of the program, the implicit trust of the developers, and the sanctity of the aforementioned marriage. In case of emergency, REVERT TO THE BACKUP. Do not induce vomiting. Whether you've edited the binary or not, they'll only blame Unsanity, so whatever you do, DON'T CALL BAREBONES BECAUSE YOU BROKE SOMETHING.

We can hope that the discourse underway on this site might encourage BareBones to elevate the sophistication and mentality of their ass-covering mechanisms in future revisions of an otherwise sophisticated and high-minded application. In the meantime, I say, hack away.

[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: wgscott on Jun 13, '05 02:11:39PM

Scoff if you want, but when I made this edit, my girlfriend left me, my dog bit me, and Nigerians obtained my bank account information.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: sjonke on Jun 13, '05 11:46:51PM

BBEdit doesn't crash. Really, it doesn't. I can't remember the last time BBEdit crashed on me. A year ago? Longer? Methinks some "haxie" (god how I hate that "term") may indeed be causing problems for you and BBEdit. Have you considered trying disabling APE and seeing what the result is? A flawed APE module can definitely cause crashes and instability. If you want to use APE without problems you have to keep up to date on it and all modules, and even then you may have problems. In spite of what they say, a hack is a hack, and hacks can cause crashes when they do things the underlying application isn't expecting, or when an application something something the hack isn't expecting.

---
--- What?



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: deleted_user18 on Jun 14, '05 01:20:56AM

Yeah right BBEdit ist the first software without flaw. Good old carbon horse. Even mathematicans proved that its code is without any bugs. Haha.

So every bug must be in APE, can't be in OS X or in some optional kernel extensions.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: Tom Robinson on Jun 14, '05 02:17:21AM

A couple of years ago I used to run FruitMenu. Both BB's Mailsmith and the Finder regularly crashed. I've since switched to Classic Menu which provides the same basic functionality but without hacking into the system to do so. No more crashes.

I know people will jump to Unsanity's defence, but the fact is it does cause problems for some people. You get that when you're hacking the system.

If Unsanity caused an increase in calls to BB's tech support because it had been injecting code into BBEdit, why not provide a warning as the first step in troubleshooting?

There was a long discussion about this on the Mailsmith mailing list, and some pretty knowledgeable guys (not from BB) berated the Unsanity people for thinking they knew better than both Apple and other app writers.

If BBEdit is regularly crashing, you're a lot better off finding the reason why instead of patching it to disable the warning.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: zot72 on Jun 14, '05 09:04:09PM

BBEdit (or Mailsmith in my case) isn't crashing for me; that's the whole problem. I've seen the damned warning countless times, and not once had Mailsmith crashed or been force quit. Because the stupid dialog is posted after a nimrod check that seems to succeed if you've ever even heard of an APE-based product, I'm left with Mailsmith repeatedly interrupting my work with a condescendingly-worded dialog telling me it is Unsanity's fault that my hardware vendor released a device driver with a hot-plug defect. Bare Bones has, therefore, tried to steal my irratation with my hardware vendor from that hardware vendor (where it belongs) and redirect it towards Unsanity. They only succeeded on the first part of that.

The hardware vendor has since released an updated driver that doesn't crash my PowerBook. Has Bare Bones released updated apps that don't post idiotic dialogs for no reason other than to piss me off? Apparently not.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: lucite on Jun 14, '05 12:53:04PM

This is ridiculous - you can have it both ways.

BareBones should have had their alert dialog show up and have a checkbox for 'never show again'. Goodness all around.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: zot72 on Jun 14, '05 09:09:37PM
Right. :) They cannot add a check (presumably) for me not being an idiot; I already try disabling APE to localize the source of a problem in the exceedingly rare case that I have one -- duh! They can, however, add a post snippy dialogs pointing out the obvious preference that I can turn the hell off.

[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: monickels on Jun 20, '05 11:43:32AM

Amen to this hint. BBEdit should take the stupid warning out altogether. When BBEdit crashes on my machine, it's because I force quit it out of a spinning beachball mode that came up because BBEdit chokes on files larger than a few megabytes. Lame. Emacs doesn't choke.



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: cp21yos on Jun 24, '05 07:23:32AM

I've been using BBEdit for as long as I can remember and since we started running web servers I've been opening up log files (usually a couple hundred mb's in size) to do some quick search work on them. Never had a problem...

So, if BBEdit is crashing on just a couple of Mbs I'd say you've got something else causing instability in your setup...



[ Reply to This | # ]
Disable BBEdit's 'APE' crash warning
Authored by: lrivers on Nov 29, '05 04:18:08PM

One thing to point out is that this dialog only appears if you have APE installed and further, it simply suggests you check to make sure that an extension is not causing the problem. The text reads:

You appear to be using one or more system additions or preference panels which employ "Application Enhancer". Application Enhancer works by running its own code inside of BBEdit and other applications. This can lead to crashes, unpredictable application behavior, and other symptoms of incompatibility. If you continue to experience problems after removing all third-party system additions and preference panels, please contact <support@barebones.com> for assistance.



[ Reply to This | # ]
Why the dialog is there in the first place
Authored by: xcgr on May 31, '06 11:52:42AM

Several commenters are questioning why BBEdit sometimes displays a warning message about Application Enhancer and 3rd-party system mods. Rich Siegel wrote an explanation in his blog: http://www.glorifiedtypist.com/2005/11/labor_saving_devices.html

Bottom line: at the time of an unexpected crash, if BBEdit detects that Application Enhancer has loaded itself into BBEdit's memory space, then you get a warning message. This seems reasonable to me. If BBEdit's memory space was altered without its knowledge, then the first logical troubleshooting step is to remove the cause of that alteration.



[ Reply to This | # ]