Hi,
I want to give everyone an update on this. We've looked at about two dozen
logs sent to us by customers on this. In *every case* the customer's
hardware included an Nvidia GeoForce Graphics card. If you are encountering
this problem and *don't* have an Nvidia GeoForce Graphics card we would
really like to know. Also, although some people have told me that they've
seen the problem even though they have not installed the Leopard Graphics
Update, every system profile except one indicated that that update was
installed on the system (and I had reason to suspect that particular
profile).
We've gathered all the information we've collected so far and posted a bug
in the Apple bug database that we use for reporting issues to them. This
isn't to say that is definitely an Apple bug, but the fact that this only
seems to happen with certain hardware makes that quite likely.
I'd also like to point people again to this thread on the Apple MacBook Pro
discussions list:
http://discussions.apple.com/thread.jspa?messageID=6706148. The reports
there look very much like people are reporting with Excel. I will let you
all posted if we get any information from Apple that will help resolve this
problem.
Thanks,
Pat
I actually am experiencing the same above.
System hangs, beachball of death, and only occurs with Excel.
12.0.1. update applied, all patches applied for 10.5.2 including Graphics
update.
Logs indicating
3/14/08 11:11:43 AM Microsoft Excel[317] CGBitmapContextGetData: invalid
context
3/14/08 11:07:25 AM kernel NVChannel(GL): Graphics channel exception! status =
0xffff info32 = 0x3 = Fifo: Unknown Method Error
The NVChannel exception occurs ONLY when Excel has "crashed" and my MBP is
locked up.
Again this does not happen with any other application, has happened with
multiple different excel spreadsheets, all created by PC users running 2003
and 2007 Office.
Also, along with the 12.0.1 update, all Hyperlinks in my workbooks have been
broken and are no longer recognized as links, but just plain text.
To reiterate about the lockup - this happens when either
1) copying and pasting between workbooks, or between spreadsheets
2) Maximizing the spreadsheet by either the green +, or dragging the window
3) Even have had it crash in this manner saving a workbook.
Like Joel above I experienced these issue prior to the 12.0.1 update.
--
Pat McMillan
Macintosh Business Unit
Microsoft Corp.
This posting is provided ³AS IS² with no warranties, and confers no rights.