Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
EXC_BAD_ACCESS is a very generic term, and doesn't apply in the way you're thinking it does. An app crash now and then is nothing to concern yourself over. It's when they are often and reproducible that you have a problem.

In this case, I think it's likely that the adblocker doesn't work with the Safari 4 beta.

In the mahjong case, it could have been an OS update that required an upgrade to the app to fix the error.

As an example, here's the beginning of an iTunes crashlog, and I don't have "Safari Adblock" installed.

Code:
Process:         iTunes [5693]
Path:            /Applications/iTunes.app/Contents/MacOS/iTunes
Identifier:      com.apple.iTunes
Version:         8.0.2 (8.0.2)
Build Info:      iTunes-8022001~2
Code Type:       X86 (Native)
Parent Process:  launchd [219]

Date/Time:       2009-02-17 14:06:48.856 -0500
OS Version:      Mac OS X Server 10.5.6 (9G55)
Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000f7298120
Crashed Thread:  0

What he said. EXC_BAD_ACCESS is not indicative of hardware failure. It is strictly a software problem.
 
How did it go?

I don't know if you were asking me, but since I posted in the thread I'll answer :)

I booted from the MBA Software Reinstall Drive and chose the option to restore OS X. That seemed to fix everything -- no more aborts.

I also re-installed Steam and my game (Civ 5) and that went OK and didn't cause any problems this time around. So that may not have been the source of the original problem.
 
Same problem, different Program

Hi you guys, I seem to have the same issue with a different program, in this case Football Manager 2010, my mac is a MacBook Pro 2010 model (2.4 Ghz running on Snow Leopard 10.6.5 if anyone could help I would really appreciate it.
 

Attachments

  • FM 2010 Crash report.doc
    68 KB · Views: 212
Looks like a graphics problem with the application. Are you all up to date with patches from the developer of the game?
 
didnt change a thing, still crashing on boot.
heres the errors, not sure of they are the same?
 

Attachments

  • Errors.doc
    86.5 KB · Views: 198
didnt change a thing, still crashing on boot.
heres the errors, not sure of they are the same?

Not sure what to tell you. At this point, I'd be contacting the Sibelius tech support for help. It may be that it's not compatible with 10.6.5 or they have a patch?
 
yes I have updated to speed, is it possible that there is an issue with the original installation disk?
 
Exc_Bad_Access issue

I recently upgraded from a March 2008 MBP (running Leopard) to a unibody MBP (previous generation, running Snow Leopard). Since then, I've noticed a Kernal Panic (which never occurred on the previous MBP) and an Exc_Bad_Access error which caused flash to crash.

In case this helps, I've also been getting some distortion from time to time when loading websites from my top site page. It appears for a few seconds and then the page loads. This is an image of the distortion that someone else posted on mac support: http://tinypic.com/r/20aum3m/7 .

Any thoughts on what the problem is and what I could do to address what's happening? I've uploaded the crash report - hope this is enough info!
 

Attachments

  • Exc_Bad_Access_Query_090311.pdf
    72.8 KB · Views: 218
Exc_Bad_Access (SIGSEGV): Dreamweaver crash on startup

After attempting to install CS5 Master Collection, Dreamweaver CS4 crashes at startup. I'm not that familiar with reading Crash Logs. Could someone have a look at the attached and give me some idea where to begin looking? Any information you'd care to provide about reading the Crash Log of diagnosing the problem would be greatly appreciated.
 

Attachments

  • Dreamweaver Crash Log.txt
    25 KB · Views: 201
Last edited:
Have this problem with EVO

hello
I have since 1 year a MAC OS X 10.6.7
(details:
Model Name: MacBook
Model Identifier: MacBook6,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.26 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
)

and I am running EVO
Koala version 2.8 Build 8

I have run meetings for a long time with
no problems, but since about two months it
happens I cannot share my desktop anymore.

I used to do this fine until March 2011, but since March 2011
whenever I try to open the Deskshare I get icon appearing on
my mac and then disappearing again immediately
followed by the appearance of the window which says

EVO_DeskShare quit unexpectedly.


If I open the log of the crash I see the report
below. Can anybody help ?
this is quite important for me as I am chairing a
regular weekly meeting and I need to broadcast
my screen all the time...
Please let me know soon

best regards
giulia

PS: I attach two logs of the same problems at different times, in case this can help...
 

Attachments

  • evo2.txt
    29 KB · Views: 160
  • evo1.txt
    25.9 KB · Views: 190
mdworker crash

Hello.

I've been getting this error constantly on one of my machines — could anyone shed some light into the culprit?

I've attached one of the many mdworker crash logs.

Any advice would be appreciated!
Kristin.
 

Attachments

  • mdworker_crash.txt
    15.8 KB · Views: 296
Hello.

I've been getting this error constantly on one of my machines — could anyone shed some light into the culprit?

I've attached one of the many mdworker crash logs.

Any advice would be appreciated!
Kristin.

mdworker, which is the search indexer crashed when processing the meta data for a file (GetMetadataForFile). That's about all I can tell from this stack trace. Probably a bug in mdworker.

Maybe try rebuilding the spotlight indices. Perhaps some metadata got corrupted and is causing the crash. Some instructions on how to do so here:
http://www.thexlab.com/faqs/stopspotlightindex.html#Anchor-Rebuilding-49575
 
hello
I have since 1 year a MAC OS X 10.6.7
(details:
Model Name: MacBook
Model Identifier: MacBook6,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.26 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 3 MB
Memory: 4 GB
Bus Speed: 1.07 GHz
)

and I am running EVO
Koala version 2.8 Build 8

I have run meetings for a long time with
no problems, but since about two months it
happens I cannot share my desktop anymore.

I used to do this fine until March 2011, but since March 2011
whenever I try to open the Deskshare I get icon appearing on
my mac and then disappearing again immediately
followed by the appearance of the window which says

EVO_DeskShare quit unexpectedly.


If I open the log of the crash I see the report
below. Can anybody help ?
this is quite important for me as I am chairing a
regular weekly meeting and I need to broadcast
my screen all the time...
Please let me know soon

best regards
giulia

PS: I attach two logs of the same problems at different times, in case this can help...

In both cases it crashed when opening the video device (whatever that means):
1 caletch.deskshare 0x0005f727 deskShare::VideoDevice::eek:pen() + 353

You should contact EVO about it instead.
 
mdworker, which is the search indexer crashed when processing the meta data for a file (GetMetadataForFile). That's about all I can tell from this stack trace. Probably a bug in mdworker.

Maybe try rebuilding the spotlight indices. Perhaps some metadata got corrupted and is causing the crash. Some instructions on how to do so here:
http://www.thexlab.com/faqs/stopspotlightindex.html#Anchor-Rebuilding-49575

Thanks, I'll give that a shot and monitor it over the next week.
k.
 
Mail crashes with SIGBUS error - often

I have read through the posts in this thread, and wonder if any of the gurus can help with this one. I run a simple script to forward selected spam messages to spam@uce.gov. Often the script will cause the SIGBUS error in the middle of sending a bunch of messages, and I can't figure out why.

I have attached the most recent log and the script, in the hope that someone can shed some light on this.

Cheers,
Allan

PS I should add that mail never crashes when doing it manually, only when running this script.
 

Attachments

  • Archive.zip
    16.3 KB · Views: 117
Exc_bad_access (sigbus)

Since I upgraded to Lion yesterday, iPhoto crashes immediately. I'm getting this
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000002218a140

Everything is up to date. I have deleted the iPhoto p.list.

Full crash report is attached.

Can anyone shed any light on what's going on ?

Many thanks

Jacques
 

Attachments

  • Process.doc
    157.5 KB · Views: 156
I'm getting these once or twice a day with BBC iPlayer Desktop:

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Always the same exception code. Been happening for the past month or so. I'm attaching the full crash dump. Anyone shed any light on this? I've fully removed/reinstalled iPlayer, AIR and Flash multiple times and it's still glitchy as hell. I've also run the extended AHT multiple times and found no hardware errors.
 

Attachments

  • crashdump.txt
    53.1 KB · Views: 433
Final Cut Pro - Crash Report - Help

Hi,

Here is the first bit of a Final Cut Pro Crash report that I keep getting. Do you think it is the Avid Codec that is causing it to crash?

THANKS! (word document of whole report is too big to attach :( )

Process: Final Cut Pro [305]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 7.0 (7.0)
Build Info: FCPApp-906181654~22
Code Type: X86 (Native)
Parent Process: launchd [178]

PlugIn Path: /Library/QuickTime/AvidAVinCodec.component/Contents/MacOS/AvidAVinCodec
PlugIn Identifier: com.avid.qtcodecs.AvidAVinCodec
PlugIn Version: 2.3.1 (2.3.1)

Date/Time: 2011-11-28 12:12:51.426 -0500
OS Version: Mac OS X 10.6.3 (10D575)
Report Version: 6

Interval Since Last Report: 139170 sec
Crashes Since Last Report: 12
Per-App Interval Since Last Report: 11161 sec
Per-App Crashes Since Last Report: 12
Anonymous UUID: 0A54FEE2-C091-43B1-B433-E3688C576E7B

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000005a310
Crashed Thread: 117
 
Help!

Hey guys
I am using an animation program and it keeps crashing at the same point. I keep getting the following error message:

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000b0211f83
Crashed Thread: 6

Can anyone tell me what the issue might be?

Thanks for the help! :apple:
 
Having the same issue

Hi everyone,

Seems I am having the same issue as most people here. It is driving me mad. I only started noticing this after upgrading the OS X Lion 10.7.4 last week. Any help would be GREATLY appreciated.

Getting the same exact software crashes as everyone else and it seems to be related to any software that deals with video. This includes:

Toast Titanium - Crashes with the error when loading a movie file into the software

Cisco Jabber Video - Video conferencing software that worked fine before but now crashes as soon as you try to launch a video call (it opens fine, just crashes as soon as any video starts, including launching my webcam for self view)

Flip4Mac - This is software to assist in playing WMV files on Mac. It fails at startup.

I have to believe I have some kind of corrupt file or something somewhere but I have no idea where to look. It is driving me nuts. Happy to attach a crash log if necessary.

Again this is the error that starts with "Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000"

Thanks in advance to anyone who might have an idea.

~Matty
 
Last edited:
What he said. EXC_BAD_ACCESS is not indicative of hardware failure. It is strictly a software problem.
Wrong! EXC_BAD_ACCESS can happen also, if the RAM overwrites itself, because it has heat or other stability problems. Many programs save pointers to functions and program data in the RAM. If the RAM overwrites itself, the OS does nothing, so it can be a hardware problem.
 
Issue Solved!!!

All just wanted to let everyone know that I solved this issue.

I didn't think it had to do with RAM because I had run a ton of RAM tests and all came back fine. After a lot of my own digging through the logs I found that the issue was caused by the Flip4Mac software.

Even though I had uninstalled it there were still some preferences files in the library that was causing the failures.

The files were:

net.telestream.wmv.plist files from the Library > Preferences folder.
3 similar files in the Library > Quicktime folder.

Once I removed these files everything was back to normal.

~Matty
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.