Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

loaddata.cpp(3079) error

I can't find any way to avoid getting a LabVIEW internal error below.  Please help:


c:\builds\penguin\labview\branches\2009\dev\source\panel\loaddata.cpp(3079) : DWarn: XML GraphCursors does not match private-data GraphCursors at item 0.
$Id: //labview/branches/2009/dev/source/panel/loaddata.cpp#1 $
0x00000001401F4076 - LabVIEW <unknown> + 0
0x0000000140FA3CC8 - LabVIEW <unknown> + 0
0x0000000140F78850 - LabVIEW <unknown> + 0
0x00000001403F9775 - LabVIEW <unknown> + 0
0x000000014008DA68 - LabVIEW <unknown> + 0
0x0000000140097457 - LabVIEW <unknown> + 0
0x000000013FEF5B86 - LabVIEW <unknown> + 0
0x00000001403FB07D - LabVIEW <unknown> + 0
0x00000001403FBDCC - LabVIEW <unknown> + 0
0x00000001403FC8AC - LabVIEW <unknown> + 0
0x000000013FEF4F0A - LabVIEW <unknown> + 0
0x000000013FF20293 - LabVIEW <unknown> + 0
0x000000013FF5FE46 - LabVIEW <unknown> + 0
0x000000013FEF5B86 - LabVIEW <unknown> + 0
0x00000001403FB07D - LabVIEW <unknown> + 0
0x00000001403FBDCC - LabVIEW <unknown> + 0
0x00000001403FC0C8 - LabVIEW <unknown> + 0
0x00000001403FC956 - LabVIEW <unknown> + 0
0x000000013FEF4F0A - LabVIEW <unknown> + 0
0x000000013FFF7F74 - LabVIEW <unknown> + 0
0x000000013FEF5B86 - LabVIEW <unknown> + 0
0x00000001403FB07D - LabVIEW <unknown> + 0
0x00000001403FBDCC - LabVIEW <unknown> + 0
0x00000001403FC8AC - LabVIEW <unknown> + 0
0x000000013FEF4F0A - LabVIEW <unknown> + 0
0x000000014006CEB5 - LabVIEW <unknown> + 0
0x00000001400E0739 - LabVIEW <unknown> + 0
0x000000013FEF5B86 - LabVIEW <unknown> + 0
0x00000001403FB07D - LabVIEW <unknown> + 0
0x00000001403FBDCC - LabVIEW <unknown> + 0
0x000000013FFEF381 - LabVIEW <unknown> + 0
0x000000013FEF5B86 - LabVIEW <unknown> + 0
0x00000001403FB07D - LabVIEW <unknown> + 0
0x00000001403FBC68 - LabVIEW <unknown> + 0
0x00000001403FD460 - LabVIEW <unknown> + 0
0x00000001403FD7AD - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address 0x        3F450000 ***
Loading VI Heap, HeapClass "FPHP", C:\Users\ikeda\Desktop\DATA ACQUISITION\PATIENT_MONITORS_GEN_II\CAPNOSTREAM GEN_02.vi
*** End Dump ***
Possible path leak, unable to purge elements of base #0

0 Kudos
Message 1 of 7
(7,423 Views)

Hi keitaikeda,

 

What version of LabVIEW are you using? 2009? 2009 SP1? 2010?

 

Do you have any patches installed as well?

 

What exactly are you doing to produce the error?

 

It looks like there are some Corrective Action Requests (CARS) that exist regarding this issue but I need a little more information to figure out which one applies to your case.

 

Thanks

 

Paul M

 

 

National Instruments | Applications Engineer | www.ni.com/support
0 Kudos
Message 2 of 7
(7,405 Views)

Hi Paul,  here are some details:


####
#Date: Tue, Feb 15, 2011 9:12:40 AM
#OSName: Windows 7 Enterprise
#OSVers: 6.1
#OSBuild: 7600
#AppName: LabVIEW
#Version: 9.0f3 64-bit
#AppKind: FDS
#AppModDate: 12/17/2009 22:31 GMT
#LabVIEW Base Address: 0x        3FE20000

 

I did notice several things:

1) There are no error codes to speak of.
2) Sometimes I get the white screen of death and it catastrophically exits, or
3) I try to close the VI and restart - The VI closes but it never gets expunged from memory.
  a) The front panel closes and in all appearances, it does seem to have closed.
  b) It doesn't show up in the task bar, it doesn't show up on the "Windows" menu of LabVIEW.
  c) It doesn't show under the Task Manager so I have to exit out of LabVIEW completely
     in order to reload the VI.
  d) However, if I try reopening the VI from Windows Explorer, it pops up with a message,
     "The VI is already in memory."  It then gives me an option to: a) discard
     changes or b) View.   If I choose the "View" the VI in memory, it never opens
     the VI.  If I choose the a) discard changes option, it loads the copy in the memory,
     complete with the old data in the front panel.  

Upon examination of the error logs, I noticed there are several failures in each of the logs:

1) c:\builds\penguin\labview\branches\2009\dev\source\panel\loaddata.cpp(3079) : DWarn: XML GraphCursors does not match private-data GraphCursors at item 0. $Id: //labview/branches/2009/dev/source/panel/loaddata.cpp#1 $

 

- The GraphCursosrs - i don't know what that is but it sounds like LabVIEW doesn't like the cursors so I deleted them in the VI.

 

2) Possible path leak, unable to purge elements of base #0
- This is ominous - I have no clue what it means and how to address this.

 

3) c:\builds\penguin\labview\branches\2009\dev\source\manager\image.cpp(14372) : DWarn: GetDC failed in ISetGPort $Id: //labview/branches/2009/dev/source/manager/image.cpp#1 $

- This sounds like a hardware error where the application call to GetDC method inside ISetGPort failed for some reason.  I do have a USB-6008.  It may be that the USB port / connections are not robust enough.

 

4)c:\builds\penguin\labview\branches\2009\dev\source\manager\drawmgr.cpp(2921) : DAbort: no HDC
$Id: //labview/branches/2009/dev/source/manager/drawmgr.cpp#1 $
- Perhaps a call to an unknown hardware.  I think I've rectified this by putting the mxDAQ call to stop inside a condition.

 

0 Kudos
Message 3 of 7
(7,400 Views)

How to reproduce errors?  I don't know.  It is spurious and unpredictable.  One day, it will be fine.  and with absolutely no change in any condition except a reboot of the computer, it will fail.

 

0 Kudos
Message 4 of 7
(7,399 Views)

Hey keitaikeda, 

 

Does this happen when you do one specific thing? If you are unsure, please take note the next time your receive this error and let us know what you were doing right before it occurred. Usually, we try to put in a Corrective Action Report with something like this, but we need to be able to reproduce the same error. We might also be able to shed more light on your troubles if you attach your code, if you are comfortable with that.

 

Cheers,

kgarrett 

0 Kudos
Message 5 of 7
(7,378 Views)

Hi - The answer is no - it fails when there is no manipulation of the front panel.  It is collecting the data, and everything seems to be going ok.  My hands are away from the keyboard and mouse.

 

Then the white screen of death appears.  Without warning and usually without an error log.

 

Puzzling...   f3 patch has been applied

 

0 Kudos
Message 6 of 7
(7,371 Views)

Hey keitaikeda, 

 

Since this error isn't reproducible, it is hard to diagnose the cause of the issue. I would recommend upgrading to 2009 SP1 or 2010, if you are able. That might fix the problem, but we have record of a few other users with various Windows operating systems still experiencing this error with 2010. The only other thing that I can think of that you may be able to do is to isolate exactly where in your code that you experience the error-highlight execution while running the code and when the white screen appears, take note of where in the code it occurred, and post on this same forum. 

 

Sorry I could not be of more help! Best of luck!

 

Cheers,

kgarrett 

0 Kudos
Message 7 of 7
(7,352 Views)