Me: I live in Silicon Valley with my wife, child and cat. I have worked at Microsoft since I graduated from College, both in the Macintosh Business Unit on products such as Outlook Express, Entourage, IE, and Virtual PC and in Windows Live on Hotmail, Calendar and People. I am currently a Principal Lead Program Manager on the Windows Live Social Networking team. I basically manage a team of Program Managers responsible for delivering features to support our web and client applications. I've been blogging since 2001 and like to play around with .NET in my spare time working on projects such as dasBlog (the blog that powers this site) and Send to SmugMug (an application for uploading photos to SmugMug). I blog about a number of technology and productivity related topics.
Powered by: newtelligence dasBlog 2.3.9074.18820
Disclaimer The posts on this weblog are provided "AS IS" with no warranties, and confer no rights. The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.
© Copyright 2010, Omar Shahine
E-mail
When I set up my new PC I started seeing the weirdest problem. Basically, whenever I launch any Office 2003 application, the process launches, sits around and does nothing for 20–30 seconds, and then the application loads.
When I look at the process in task manager, the process is there and has a 72k working set. It’s the same for ever app. After 20 – 30 seconds the working set increases to normal. I looked at the launches in Filemon and Regmon and can’t seen to see anything special except that there are gaps of 10 and 20 seconds where nothing is happening.
I did a few searches and found nothing (this is one of those things that is hard to search for). But today, I was talking to one of my PMs, Andy, and when I explained what was happening he screamed that he was having the same problem. We both mentioned how we were considering flattening our boxes. But now that we both have this problem, we suspect a bug. It also turns out we have brand new pentium 4 chips (mine is a dual core, Andy’s is a single core).
So, since Andy was a former Powerpoint developer, he is going to try and debug using symbols so we can find out what is going on.
Has anyone else seen this?
update: upgrading to Office 2003 SP2 seems to have resolved this problem. yay!