Office 2008 is verbose

[Jeremy]

Hi,

I just got the new Office 2008 and apparently it likes talking to the console...

Hear is an extract from my system.log file (Leopard fully up to date):
Jan 18 22:31:00 macbook-de-jeremy Microsoft Excel[2353]: CGBitmapContextGetData: invalid context
Jan 18 22:31:30: --- last message repeated 5 times ---
Jan 18 22:31:58 macbook-de-jeremy Microsoft Word[2360]: CGBitmapContextGetData: invalid context
Jan 18 22:32:28: --- last message repeated 139 times ---
Jan 18 22:32:38 macbook-de-jeremy Microsoft Word[2360]: CGBitmapContextGetData: invalid context
Jan 18 22:32:40: --- last message repeated 39 times ---
Jan 18 22:32:40 macbook-de-jeremy Microsoft Excel[2353]: CGBitmapContextGetData: invalid context
Jan 18 22:33:10: --- last message repeated 5 times ---

I thought you should know. This would make the system.log unnecessarily big.

Thanks

 

[William Smith]

Hi,

I just got the new Office 2008 and apparently it likes talking to the
console...

Hear is an extract from my system.log file (Leopard fully up to date):
Jan 18 22:31:00 macbook-de-jeremy Microsoft Excel[2353]:
CGBitmapContextGetData: invalid context
Jan 18 22:31:30: --- last message repeated 5 times ---
Jan 18 22:31:58 macbook-de-jeremy Microsoft Word[2360]:
CGBitmapContextGetData: invalid context
Jan 18 22:32:28: --- last message repeated 139 times ---
Jan 18 22:32:38 macbook-de-jeremy Microsoft Word[2360]:
CGBitmapContextGetData: invalid context
Jan 18 22:32:40: --- last message repeated 39 times ---
Jan 18 22:32:40 macbook-de-jeremy Microsoft Excel[2353]:
CGBitmapContextGetData: invalid context
Jan 18 22:33:10: --- last message repeated 5 times ---

I thought you should know. This would make the system.log unnecessarily
big.

Not necessarily unnecessarily. (How's that for a play on words?)

First, I appreciate the fact that Office is now providing logging
information. All applications should do this.

An application's name associated with a log entry doesn't necessarily
mean that it's that application writing to the log. In fact, I see this
message with Word 2004 and it doesn't write log files.

I'm not a developer so I can't tell you anything about this particular
set of entries. But so long as your Mac is allowed to run its
maintenance routines (rotating and deleting log files) and the entries
aren't writing so much information that your drive fills up then this
shouldn't be an issue.

Hope this helps!

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>

 

[willtisdale]

Hi,

I just got the new Office 2008 and apparently it likes talking to the
console...

Hear is an extract from my system.log file (Leopard fully up to date):
Jan 18 22:31:00 macbook-de-jeremy Microsoft Excel[2353]:
CGBitmapContextGetData: invalid context
Jan 18 22:31:30: --- last message repeated 5 times ---
Jan 18 22:31:58 macbook-de-jeremy Microsoft Word[2360]:
CGBitmapContextGetData: invalid context
Jan 18 22:32:28: --- last message repeated 139 times ---
Jan 18 22:32:38 macbook-de-jeremy Microsoft Word[2360]:
CGBitmapContextGetData: invalid context
Jan 18 22:32:40: --- last message repeated 39 times ---
Jan 18 22:32:40 macbook-de-jeremy Microsoft Excel[2353]:
CGBitmapContextGetData: invalid context
Jan 18 22:33:10: --- last message repeated 5 times ---

I thought you should know. This would make the system.log unnecessarily
big.

Not necessarily unnecessarily. (How's that for a play on words?)

First, I appreciate the fact that Office is now providing logging
information. All applications should do this.

An application's name associated with a log entry doesn't necessarily
mean that it's that application writing to the log. In fact, I see this
message with Word 2004 and it doesn't write log files.

I'm not a developer so I can't tell you anything about this particular
set of entries. But so long as your Mac is allowed to run its
maintenance routines (rotating and deleting log files) and the entries
aren't writing so much information that your drive fills up then this
shouldn't be an issue.

Hope this helps!

--

bill

William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <http://entourage.mvps.org/>
Entourage Help Blog <http://blog.entourage.mvps.org/>

To be honest, I don't believe it does help. My Word 2008 spewed 560 of
these entries out in 20 seconds. Now, are you telling me that is
right!!!!!

Now, assuming you use it for an hour, and it keeps on with that number
of entries, that is 100800 entries, which is going to kinda fill the
logs and disks at an alarming rate.

So, you are wrong, it will be an issue, and MS should have fixed it
before release.

 

[JE McGimpsey]

To be honest, I don't believe it does help. My Word 2008 spewed 560 of
these entries out in 20 seconds. Now, are you telling me that is
right!!!!!

The logs entries show some sort of problem with graphic images ("invalid
data" doesn't tell *me* much, at least) in Word and XL.

Without knowing what image calls are causing the problem, it's
impossible for anyone to say what's "right".

Now, assuming you use it for an hour, and it keeps on with that number
of entries, that is 100800 entries, which is going to kinda fill the
logs and disks at an alarming rate.

I can't reproduce your results - I worked for over an hour this morning
with a Word document containing multiple images without getting a single
error message.

Is your assumption valid for your machine?

Do you continue to get these errors at that rate? Are you doing anything
in particular when they occur?

Do you get these errors from Word and XL while working on different
files?

So, you are wrong, it will be an issue, and MS should have fixed it
before release.

Since it's not happening universally, it won't be an issue for everyone.

However, you should use Help/Send Feedback to report it to MacBU.

 

[netnothing]

I am having this issue as well. I can confirm that atleast 2 other users are seeing this in their logs as well.

I don't have to do anything other than open any Office 2008 app. Just doing that will result in the following errors:

Jan 28 15:49:57 computername Microsoft Excel[35241]: CGBitmapContextGetData: invalid context
Jan 28 15:49:58: --- last message repeated 29 times ---
Jan 28 15:49:58 computername Microsoft Word[35225]: CGBitmapContextGetData: invalid context
Jan 28 15:49:59: --- last message repeated 14 times ---
Jan 28 15:49:59 computername Microsoft Excel[35241]: CGBitmapContextGetData: invalid context
Jan 28 15:50:22: --- last message repeated 49 times ---
Jan 28 15:50:22 computername Microsoft Word[35225]: CGBitmapContextGetData: invalid context
Jan 28 15:50:30: --- last message repeated 100 times ---
Jan 28 15:50:30 computername Microsoft Excel[35241]: CGBitmapContextGetData: invalid context
Jan 28 15:51:00: --- last message repeated 189 times ---
Jan 28 15:51:00 computername Microsoft Excel[35241]: CGBitmapContextGetData: invalid context
Jan 28 15:51:14: --- last message repeated 59 times ---
Jan 28 15:51:14 computername Microsoft Word[35252]: CGBitmapContextGetData: invalid context
Jan 28 15:51:44: --- last message repeated 324 times ---