Starting memory profile in Library causes LV to crash

[twols]

Hello!

When I'm working on a library with many classes labview crashes sometimes. Today I was able to trigger the crash manually.... Even on an empty library, if I try to start the memory profiling tool, LV crashes..

####
#Date: Mi, 23. Jan 2013 10:02:58
#OSName: Windows 7 Enterprise Service Pack 1
#OSVers: 6.1
#OSBuild: 7601
#AppName: LabVIEW
#Version: 12.0f3 32-bit
#AppKind: FDS
#AppModDate: 10/04/2012 15:12 GMT
#LabVIEW Base Address: 0x00400000



<DEBUG_OUTPUT>
23.01.2013 10:03:16.550
Crash 0x0: Crash caught by NIER
File Unknown(0) : Crash 0x0: Crash caught by NIER
minidump id: 381ce9c1-0956-48de-86cf-0ac5f02c36cd
ExceptionCode: 0xC0000005

</DEBUG_OUTPUT>
0x01AF1179 - LabVIEW <unknown> + 0
0x01AF1688 - LabVIEW <unknown> + 0
0x7C37FDB4 - MSVCR71 <unknown> + 0
0x77B574DF - ntdll <unknown> + 0
0x77B19EC5 - ntdll <unknown> + 0
0x00000000 - <unknown> <unknown> + 0

Is it a bug?

[josborne]

If you call NI Support, the first two querstions they'll ask are:

- Tell me exactly what OS and version of LV you are using, and what drivers and HW you are using (eg DAQmx, etc).

- Tell me the exact steps needed to produce this crash? 

[twols]

I'm using a Win 7 64 bit, LV 2012 32 bit patch 5.

Reproducing the crash:

* Start LV

* Go to New > Library

In the library window:

* Go to Tools > Profile > Performance and Memory

LV should crash.

[OlegS]

Dear Customer,

I could reproduce this crash on LV2012 and also on LV2011.
So it seems to be a Bug and I'm going to write an CAR to R&D so it can be fixed as soon as possible.

Thank you for your cooperation.

Regards,
Oleg Scherling, M.Eng | Applications Engineering | National Instruments | NIG