Forum Discussion

SamMackrill's avatar
SamMackrill
New Contributor
12 years ago

Exception with Allocation Profiler



VS2010 compilers


.NET 4 + Native windows x86


Windows-7 x64 on a VM machine


The build is on a ClearCase dynamic view


Using AQTime x64 Version: 7.40.800.64



Extended Debugger for Managed code OFF



When profiling a few dlls in my application, on exiting the app QAtime fails to produce any results.

I see an access violation as the last entry in the Event Viewer:



Event Thread ID Time


First chance exception 0xC0000008 INVALID_HANDLE occurred at 0x773112F7 36636 12:27:26:895


Event Thread ID Time


0x774BF9D2 NtClose + 0x12 in ntdll.dll 36636 12:27:26:895


0x752F1438 CloseHandle + 0x28 in kernel32.dll 36636 12:27:26:895


0x580C8C41 _close + 0x291 in msvcr100d.dll 36636 12:27:26:895


0x580C8B52 _close + 0x1A2 in msvcr100d.dll 36636 12:27:26:895


0x58022C34 _fclose_nolock + 0xB4 in msvcr100d.dll 36636 12:27:26:895


0x58022B3D fclose + 0xCD in msvcr100d.dll 36636 12:27:26:895


0x580229E1 _fcloseall + 0xA1 in msvcr100d.dll 36636 12:27:26:895


0x5802159A __iob_func + 0x16A in msvcr100d.dll 36636 12:27:26:895


0x5800866C _initterm + 0x1C in msvcr100d.dll 36636 12:27:26:895


0x58008514 _amsg_exit + 0x414 in msvcr100d.dll 36636 12:27:26:895



I ran though the troubleshooter but I cannot save all the events as this crashes QAtime with a resource allocation error










2 Replies

Sort By
  • SamMackrill's avatar
    SamMackrill
    New Contributor
    12 years ago
    The same thing happens on a real XP (x86) machine, running the same executable and using AQtime 6.50
  • aqAnt's avatar
    aqAnt
    SmartBear Alumni (Retired)
    12 years ago

    Hi Sam,


    Please follow the steps below:



    1. Open the Options | Options... | Profiling Time | Event View | Display events in settings page.

    2. Activate the XML Files option and specify the file name.

    3. Deactivate the Event View Panel option and save the changes.


    Now, you can get the Event View panel's contents in the XML file and complete our AQtime Troubleshooter to investigate the problematic situation.