On 12/16/09 12:34 PM, in article (e-mail address removed)2ac0,
> "
[email protected]" wrote:
>
>
> There are Microsoft fonts that are problematic with Snow Leopard. See this
> page for instructions on how to remove.
>
> Fonts to delete after installing Snow Leopard (includes help deleting font
> caches)
>
>
>
>
> Re-installing software rarely fixes problems like this. It's more important
> that you are updated. Check the Microsoft Component Plugin and see if it's
> 12.2.3 (or if you have Exchange and use EWS, 13.0.3 is the latest.)
>
> "/Applications/Microsoft Office
> 2008/Office/MicrosoftComponentPlugin.framework"
>
> When you crash, check the crash logs (you might need to select view log) and
> see if you see WebCore or JavaScriptCore in the logs. See these examples:
>
>
>
> If you are getting something different, just copy the first part as shown in
> the example in your reply.
>
> RE: WebCore & JavaScriptCore crashes
>
> The speed you click through the messages affects the crash. Entourage is not
> having enough time to render the message and some messages include links to
> images on the web which take more time.
>
> Try this workaround.
>
> 1. Simply going slower through messages can stop the crashes.
> 2. Set Entourage Preferences > Security to _Never_ download pictures. You
> would need to click on the link in each message to show pictures.
>
> --
> Diane Ross, Microsoft Mac MVP
> Entourage Help Page
> Entourage Help Blog
> YouTalk Twitter: follow
Diane,
Thanks for your help with this. I made the changes you suggested and it is definitely not crashing near as much. In fact, only once since. here is the log from the crash:
Microsoft Error Reporting log version: 2.0
Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2009-12-18 06:12:41 -0500
Application Name: Microsoft Sync Services
Application Bundle ID: com.microsoft.entourage.syncservices12
Application Signature: MSS1
Application Version: 12.2.3.091001
Crashed Module Name: unknown
Crashed Module Version: unknown
Crashed Module Offset: unknown
Blame Module Name: unknown
Blame Module Version: unknown
Blame Module Offset: unknown
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Thread 0 crashed:
# 1 0x63617474 in ( + 0x00000000)
# 2 0x95e3c509 in _objc_assign_strongCast + 0x95D8B4EB (libobjc.A.dylib + 0x0000a509)
# 3 0x91fb311b in .objc_class_name_ISDGlobalId + 0x91E621B7 (SyncServices + 0x0007511b)
# 4 0x0001c586 in __mh_execute_header + 0x0001B586 (Microsoft Sync Services + 0x0001b586)
# 5 0x0001bbe8 in __mh_execute_header + 0x0001ABE8 (Microsoft Sync Services + 0x0001abe8)
# 6 0x0001b7ee in __mh_execute_header + 0x0001A7EE (Microsoft Sync Services + 0x0001a7ee)
# 7 0x0000c0fc in __mh_execute_header + 0x0000B0FC (Microsoft Sync Services + 0x0000b0fc)
# 8 0x0000274a in __mh_execute_header + 0x0000174A (Microsoft Sync Services + 0x0000174a)
# 9 0x00002671 in __mh_execute_header + 0x00001671 (Microsoft Sync Services + 0x00001671)
X86 Thread State:
eax: 0x6e656d68 ebx: 0x937ccc08 ecx: 0x93810acc edx:0x656a624f
edi: 0x16dd09d0 esi: 0x00000000 ebp: 0xbffff768 esp:0xbffff71c
ss: 0x0000001f eip: 0x63617474 cs: 0x00000017 ds:0x0000001f
es: 0x0000001f fs: 0x00000000 gs: 0x00000037 eflags:0x00010246
Thread 1:
# 1 0x95a400ea in __dispatch_hw_config + 0x95883162 (libSystem.B.dylib + 0x000270ea)
# 2 0x95a3fcc3 in __dispatch_hw_config + 0x95882D3B (libSystem.B.dylib + 0x00026cc3)
# 3 0x95a3fa68 in __dispatch_hw_config + 0x95882AE0 (libSystem.B.dylib + 0x00026a68)
# 4 0x95a3f4f1 in __dispatch_hw_config + 0x95882569 (libSystem.B.dylib + 0x000264