Office X reliability since 10.2? Mine has gone down. Yours?

[smith]

I would like to ask if others have noticed a degradation in Office X reliability since the upgrade to 10.2. I certainly have, and several other people I know have similar problems. My wife and I both find that Microsoft Word will "unexpectedly quit" especially when saving documents. I have also had it quit opening documents. I've looked for other threads on this topic but haven't noticed any sort of groundswell of opinion on the matter -- is it just me? (Us?)

[hschickel]

I've noticed the same thing. I get a lot of errors like the following in the console:

Sep 29 23:05:41 HSchickel1 /Applications/Microsoft Office X/Microsoft Entourage: *** Warning: Line option kATSLineIsDisplayOnly has been deprecated. ***

Sep 29 23:05:41 HSchickel1 /Applications/Microsoft Office X/Microsoft Entourage: *** Warning: ATSUMeasureText has been deprecated. Use ATSUGetUnjustifiedBounds instead. ***

I'm starting to migrate away from MS Office for this reason.

Hugh

[mervTormel]

hmm, just had a Word "crash" on a "save" file operation. but, my edits were saved. then i made several 100 edit/saves without a problem. but, i haven't had any issues with excel or eRage. my Word crash log indicates routine 'memmove'...

Date/Time: 2002-09-29 17:07:07 -0700
OS Version: 10.2.1 (Build 6D52)
Host: gunther.local.

Command: Microsoft Word
PID: 2353

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x018ca000

Thread 0 Crashed:
#0 0x90074d1c in memmove
#1 0x00dd07c0 in 0xdd07c0
...

i suspect this is related to some jiggery-pokery MS does with fast-saves and re-arranging the filespace in memory. what's your crash log say?

hugh, as for the "error" messages. those are warnings to developers that a routine has been deprecated (obsoleted) and that, for now, it's valid, but soon, will be a crashy type operation. so, those are more of an "early warning system" for developers.

[smith]

As above, once Word gets the first crash out of its system, subsequent saves/edits go without incident. What is going on, I have no idea, but the suggestion for fast save probably isn't my problem -- I have this turned off by default and never turn it on (since word 4, I think, or whenever it came and caused so much trouble...)

Here's my crash log, for what it is worth:

Date/Time: 2002-09-11 12:09:05 -0700
OS Version: 10.2 (Build 6C115)
Host: memex.local.

Command: Microsoft Word
PID: 1798

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0x07d20009

Thread 0 Crashed:
#0 0x90223df4 in GetHandleSize
#1 0x00df84c8 in 0xdf84c8
#2 0x00df83b4 in 0xdf83b4
#3 0x00df8300 in 0xdf8300
#4 0x00df8290 in 0xdf8290
#5 0x0034743c in 0x34743c
#6 0x003459e8 in 0x3459e8
#7 0x00343dc4 in 0x343dc4
#8 0x0095efd0 in 0x95efd0
#9 0x91b56e4c in aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*)
#10 0x91b597f0 in dispatchEventAndSendReply(AEDesc const*, AEDesc*)
#11 0x91b56d5c in aeProcessAppleEvent
#12 0x92c82d30 in AEProcessAppleEvent
#13 0x0021f728 in 0x21f728
#14 0x00a52c94 in 0xa52c94
#15 0x00dd1e18 in 0xdd1e18
#16 0x00dd1d1c in 0xdd1d1c
#17 0x92ba25b4 in DispatchEventToHandlers
#18 0x92ba291c in SendEventToEventTargetInternal
#19 0x92ba5d28 in SendEventToEventTargetWithOptions
#20 0x92bb2134 in ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)
#21 0x92ba266c in DispatchEventToHandlers
#22 0x92ba291c in SendEventToEventTargetInternal
#23 0x92bb4c88 in SendEventToEventTarget
#24 0x00df54fc in 0xdf54fc
#25 0x002c0110 in 0x2c0110
#26 0x001ff2c0 in 0x1ff2c0
#27 0x00f4bdac in 0xf4bdac
#28 0x001fed08 in 0x1fed08

[mervTormel]

well, one thing is evident. MS needs to update their OSX apps. and, hopefully, introduce less bugs rather than more.

but, this is rather typical. many apps needed tweeking to make the jump to jaguar. and it's more the exception than the rule.

but, whereas a small app by a lone developer can be changed swiftly, a large app by a monolithic developer has many "hoops" to jump thru and the oppressive weight of their tyranny is felt by their own squires. with size comes bureaucracy.

ironically, it makes the old saw "save often", well, ironic.

[hschickel]

as for the "error" messages. those are warnings to developers that a routine has been deprecated (obsoleted) and that, for now, it's valid, but soon, will be a crashy type operation. so, those are more of an "early warning system" for developers.

merv,

This is good to know. I have not tried to track down the problems much more than this - just noticed that all machines running jag have less stable offices.

Hugh