EXC_BAD_ACCESS (SIGBUS)

Question

Level 1

4 points

EXC_BAD_ACCESS (SIGBUS)

Hi ,

I'm running Pro Tools 8 and the program is crashing literally 10-15 times per day (at random) with the following system error (mac not pro tools).

Exception Type: EXC BADACCESS (SIGBUS)
Exception Codes: KERN PROTECTIONFAILURE at 0x0000000000000005
Crashed Thread: 0

I googled EXC BADACCESS (SIGBUS) and it this seems to be a big problem for an awful lot of people running all sorts of apps. The sheer amount of coverage this error has got on the net, I'm amazed Apple haven't produced an official fix for it.
Please can somebody look into this. I and others like me would be most grateful.
I'm sure I haven't put enough tech info here but a quick google search on the error will bring you back thousands of EXC BADACCESS (SIGBUS) instances.

Best

llionr

Mac Pro, Mac OS X (10.5.6), EXC_BAD_ACCESS (SIGBUS)

Posted on Apr 20, 2009 3:37 PM

Reply

Answer 1

Dogcow-Moof

Level 8

36,185 points

Apr 20, 2009 4:17 PM in response to llionr

It's a standard error that occurs when an application accesses memory that doesn't exist - in this case memory location "5."

The crash report you gave suggests it is Pro Tools, not your Mac, that is crashing as the information you supplied is an application crash report.

The very first thing I suggest you do is check with Digidesign Technical Support to make sure your hardware/software configuration is supported.

For example, for the Mac Pro, they specifically state:

All Mac Pro models are officially qualified *up to but not including* latest models announced March 3, 2009

Reply

Answer 2

Apr 23, 2009 11:58 AM in response to Dogcow-Moof

I have a similar problem (except it is at location 10 not 5) but it is for Papers.

From what I've read on the web, this is not a problem with the program software, but rather with some sort of user permission.

Apple needs to get on this, there are literally hundreds of reports about it on the web.

Reply

Answer 3

Dogcow-Moof

Level 8

36,185 points

Apr 23, 2009 2:36 PM in response to Ari Adland

Papers? Do you mean Pages?

Regardless, permissions errors are not going to cause a bus error.

Reply

Answer 4

PommeC

Level 1

0 points

Jul 6, 2009 7:26 AM in response to llionr

It happened to me with Fireworks, and I solved it by deleting some fonts I installed recently. In this case it was Impact Label, but I guess other fonts can cause this problem.
Try deleting fonts you recently installed to check if it will solve your issue.

Reply

Answer 5

Pondini

Level 8

38,863 points

Jul 6, 2009 4:04 PM in response to Ari Adland

Ari Adland wrote:

Apple needs to get on this, there are literally hundreds of reports about it on the web.

You are not talking to Apple here, just us other users.

And again, it's normally not an Apple/OSX problem, but a problem with a specific application. That's why you should have a +crash log+ when this happens. If it's an Apple application, and you get the message with an option to Report the problem, that will send it to Apple. If it's a 3rd-party app, contact the maker and send the report to them. You should be able to find it via the Console app (in your Applications/Utilities folder). When it opens, click +Show Log List+ and navigate in the sidebar to one of the +Crash Reporter+ folders.

Reply

Answer 6

Jul 14, 2009 11:05 AM in response to Pondini

Well it is starting to be a problem with Apple. I first started getting this error with Google Earth. Now it happens with Software Update and Installer. I cant update my Mac or install from .pkg files.

Does anyone have any suggestions on how to fix this?

Reply

Answer 7

Pondini

Level 8

38,863 points

Jul 14, 2009 12:24 PM in response to hackettjAZ

hackettjAZ wrote:
Well it is starting to be a problem with Apple. I first started getting this error with Google Earth. Now it happens with Software Update and Installer. I cant update my Mac or install from .pkg files.

Does anyone have any suggestions on how to fix this?

It sounds like you might have a corrupted file system. Use Disk Utility (in your Applications/Utilities folder) to do a +Verify Disk+ (not permissions) on your internal HD. If that shows errors, you'll have to boot from your Leopard Install disc and use it's copy of DU to fix them. Post back if you need to do this but don't know how.

Reply

Answer 8

Aug 23, 2009 5:29 PM in response to Pondini

I get this same error, only its the Dock that's crashing. Every time I boot up the MBP, this error appears in the CrashReporter log. I was getting a message box with the same error (at boot) until I reloaded the OS. Now it just appears in the log. I posted in another thread that I'm also having the occasional lockup and "no airport card installed" messages. I have no idea if these items are related or not, but I thought I'd mention it in case it helps someone figure out their own issue.

I'm waiting for Snow Leopard to see if the problem goes away (i.e. an OS problem). If it doesn't, I'm heading into the Apple Store I guess.

Reply

Answer 9

Sep 14, 2009 2:21 AM in response to llionr

Hi,
I get the same error with Protools HD8.0.1 when using A.I.R Hybrid.

Any Help, on duc noone?

Reply

Answer 10

Sep 21, 2009 4:35 AM in response to Community User

Not sure if this is going to help you or not DasLicht, but I had a similar problem with ProToolsLE 8 upgrade. I 'cured' the problem by downloading the 'Third Party Content' that came with the upgrade and running the installers.

The problem was with MelodyneEssential, one of the ProTools plug-ins (DigiRewire) was referencing an out-of-date file within it and causing it to crash. Once I'd ran the installer with the newer version from the Third Party Content, it worked fine.

Hope that helps!

Reply