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
How did it go?
didnt change a thing, still crashing on boot.
heres the errors, not sure of they are the same?
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.
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...
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
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.What he said. EXC_BAD_ACCESS is not indicative of hardware failure. It is strictly a software problem.