Crash when exiting MS Project 2010 Standard RRS feed

  • Question

  • I am trying to develop a managed code addin for MS Project 2010, to create a custom ribbon with some simple macros, however every time I exit Project, I get a dialog box:

    Microsoft Project has encountered a problem and needs to close.  We are sorry for the inconvenience.

    If you were in the middle of something, the information you were working on might be lost.

    [x] Restart Microsoft Project                                                                                                     [ Close ]

    I have tried to strip things out one by one to have the simplest way of reproducing the problem.

    How to reproduce

    Download the RibbonAddin_VB example from the MS Project 2010 SDK, build and install.

    Create a blank project in MS Project 2010 standard. 

    Alt-F11 and insert a blank module, save as project.mpp.  Configure trust setting to disable macros with notification. Exit.

    Open the project, click enable macros when prompted, wait for the ribbon to appear and then exit.

    When the project file is on a slow drive (such as my network drive), the crash appears every single time the application closes.  With the call stack from WinDbg as at the end of this post.

    This always happens on my XP machines (3 different ones) but not yet on my W7(x64) machine.

    If anyone has any ideas on what this might be, how to debug it or analyse it further, or a more appropriate forum to post the question, I would be very grateful.



    Call stack:

    ChildEBP RetAddr  
    0012f978 5ad747be uxtheme!CAutoCS::CAutoCS+0x11
    0012f990 5ad74792 uxtheme!CRenderList::CloseRenderObject+0x16
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for C:\Program Files\Common Files\Microsoft Shared\office14\riched20.dll -
    0012f9ac 420a0d05 uxtheme!CloseThemeData+0x1f
    WARNING: Stack unwind information not available. Following frames may be wrong.
    0012f9c8 4208a149 riched20!IID_ITextHost2+0x2b745
    0012f9dc 4208a025 riched20!IID_ITextHost2+0x14b89
    0012f9ec 42031688 riched20!IID_ITextHost2+0x14a65
    0012fa30 42031542 riched20+0x1688
    0012fa3c 7c90118a riched20+0x1542
    0012fa5c 7c9224ca ntdll!LdrpCallInitRoutine+0x14
    0012fae0 7c81caae ntdll!LdrShutdownProcess+0x14f
    0012fbd4 7c81cb26 kernel32!_ExitProcess+0x42
    0012fbe8 79fdab76 kernel32!ExitProcess+0x14
    0012fe10 79f212e0 mscorwks!SafeExitProcess+0x157
    0012feac 790237d5 mscorwks!DisableRuntime+0xdc
    0012febc 79018639 mscoree!CorExitProcess+0x48
    0012fecc 785421ae mscoree!ShellShim_CorExitProcess+0x20
    0012fed8 785421c2 MSVCR90!__crtCorExitProcess+0x29 [f:\dd\vctools\crt_bld\self_x86\crt\src\crt0dat.c @ 716]
    0012fee4 78542410 MSVCR90!__crtExitProcess+0xd [f:\dd\vctools\crt_bld\self_x86\crt\src\crt0dat.c @ 722]
    0012ff28 78542466 MSVCR90!doexit+0x10a [f:\dd\vctools\crt_bld\self_x86\crt\src\crt0dat.c @ 644]
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for winproj.exe -
    0012ff3c 2e0043af MSVCR90!exit+0x11 [f:\dd\vctools\crt_bld\self_x86\crt\src\crt0dat.c @ 412]

    Tuesday, January 15, 2013 10:24 PM

All replies

  • It might be due to the network drive

    Try to reproduce the issue on the local drive instead network storage

    Try to Enable all macros(not recommended; potentially dangerous code can run)

    Cheers. Happy troubleshooting !!! Sriram E - MSFT Enterprise Project Management

    Thursday, January 17, 2013 2:36 AM
  • Hi

    Thanks for the reply.  It works fine on my local drive though it makes no difference if I trust all macros (it still crashes).

    Interestingly, if I open project, then open the file from the network drive it is okay.

    The whole thing smells like some kind of race condition, affected by timings etc.  I have found that the exact same bug appears in all other ways too.

    Can anyone confirm that deploying project 2010 addins via vsto to create custom ribbons IS supported on XP?  And are there any constraints in terms of specific versions of dll, fixes etc that might give rise to this kind of bug?

    Debugging wise, I have put a msg box in the addin unload function to allow me to attach WinDbg.  Running the code then also gives the same stack dump at the crash.  If anyone can suggest a debugging approach via WinDbg that might help me narrow down the problem, that would also be very helpful.



    Thursday, January 17, 2013 9:48 AM