LabView crash

[Tom_Gloor]

My application was running fine for more than 400 hours. Then it suddenly crashed on a weekend. LabView wouldent respond anymore and I had to stop it manually with the windows task manager. Could anyone tell me what the cause of the crash could have been?

#Date: Do, 21. Feb 2013 12:44:45
#OSName: Microsoft Windows XP Service Pack 3
#OSVers: 5.1
#OSBuild: 2600
#AppName: LabVIEW
#Version: 11.0 32-bit
#AppKind: FDS
#AppModDate: 06/22/2011 10:12 GMT
#LabVIEW Base Address: 0x00400000



23.03.2013 03:14:44.819
DWarn 0xA0DA1F92: Bogus font
c:\builds\penguin\labview\components\LVManager\trunk\11.0\source\fontmgr.cpp(7856) : DWarn: Bogus font
minidump id: b76c636b-a52d-47c8-b4ef-35e917048e6e
$Id: //labview/components/LVManager/trunk/11.0/source/fontmgr.cpp#6 $
0x006A8973 - LabVIEW <unknown> + 0
0x10015F30 - mgcore_SH_11_0 <unknown> + 0
0x01B1788C - LabVIEW <unknown> + 0
0x01B178D9 - LabVIEW <unknown> + 0
0x00F80926 - LabVIEW <unknown> + 0
0x01012B0F - LabVIEW <unknown> + 0
0x0101538A - LabVIEW <unknown> + 0
0x0101894D - LabVIEW <unknown> + 0
0x00DE58E7 - LabVIEW <unknown> + 0
0x00C99920 - LabVIEW <unknown> + 0
0x00CF0EEC - LabVIEW <unknown> + 0
0x00C99920 - LabVIEW <unknown> + 0
0x00B8893A - LabVIEW <unknown> + 0
0x0100595A - LabVIEW <unknown> + 0
0x00C26EC4 - LabVIEW <unknown> + 0
0x00C27195 - LabVIEW <unknown> + 0
0x00FE4B9D - LabVIEW <unknown> + 0
0x00DD1995 - LabVIEW <unknown> + 0
0x00CC13D5 - LabVIEW <unknown> + 0
0x00DEC8F3 - LabVIEW <unknown> + 0
0x00C9AB63 - LabVIEW <unknown> + 0
0x00CF1351 - LabVIEW <unknown> + 0
0x00C9AB63 - LabVIEW <unknown> + 0
0x00D0D5C7 - LabVIEW <unknown> + 0
0x00C9AB63 - LabVIEW <unknown> + 0
0x00D673FA - LabVIEW <unknown> + 0
0x00C9AB63 - LabVIEW <unknown> + 0
0x00E2AFEA - LabVIEW <unknown> + 0
0x00C9AB63 - LabVIEW <unknown> + 0
0x01309294 - LabVIEW <unknown> + 0
0x0130A2AE - LabVIEW <unknown> + 0
0x0130BD0D - LabVIEW <unknown> + 0
0x0130C405 - LabVIEW <unknown> + 0
0x0130C690 - LabVIEW <unknown> + 0
0x0130CF0F - LabVIEW <unknown> + 0
0x013048E9 - LabVIEW <unknown> + 0

[josborne]

Wow that is almost impossible to guess.  First, I would forward that crash report to NI technical support. 

Then I would have a look at the Windows Event Log at the time of the crash.  Maybe you can find some clues there.

Then I would re-run my application, but do this:

1.  Setup "perfmon" in Windows to monitor memory and CPU usage while your VI is running.  Then if a crash occurs again, you can go back to check if memory wass leaking, etc.

2.  Add a log file to your VI, and have your VI record lots of info to the log file. So if a crash occurs again, you can have some clues as to what was hapenning at the time.

Its basically like a forensic study.  And you probably won't get too far unless the crash occurs again.  And if it does, you want to make sure you have lots of clues as to what is the cause.

[josborne]

This thread may also provide some clues:

http://forums.ni.com/t5/Real-Time-Measurement-and/Temp-file-with-a-possible-path-leak-is-filling-my-...