Error 1724

[lippoi]

Hi,

I get very often and randomly (i.e. average of 1/10 when I push a button of my application) the folowing error Error 1724:

####
#Date: mer. 13 déc. 2006 15:56:56
#OSName: Windows NT
#OSVers: 5.1
#AppName: LabVIEW
#Version: 8.2
#AppKind: FDS
#AppModDate: 08/19/2006 19:22 GMT



.\panel\graphcrs.cpp(1724) : DAbort: Couldn't find private data
$Id: //labview/branches/Europa/dev/source/panel/graphcrs.cpp#16 $
0x007A99D1 - LabVIEW <unknown> + 0
0x007AC0CF - LabVIEW <unknown> + 0
0x007AC4B0 - LabVIEW <unknown> + 0
0x0089924A - LabVIEW <unknown> + 0
0x008873DF - LabVIEW <unknown> + 0
0x00C0580E - LabVIEW <unknown> + 0
0x008800E3 - LabVIEW <unknown> + 0
0x00C0580E - LabVIEW <unknown> + 0
0x008802D6 - LabVIEW <unknown> + 0
0x00C0580E - LabVIEW <unknown> + 0
0x00884854 - LabVIEW <unknown> + 0
0x00C0580E - LabVIEW <unknown> + 0
0x008800E3 - LabVIEW <unknown> + 0
0x00C0580E - LabVIEW <unknown> + 0
0x008FCBB8 - LabVIEW <unknown> + 0

I recognized two buttons of my application that Induce this error. (other buttons never induce any problems)
My application communicate with a Scope using the communication protocol VISA VICP. It brakes mosty when I request a waveform with a special conditions. The use of the communication protocol on other subvi do never make it braking.
I got this error twice  with my "read  waveform" procedure. That make me think that the communication protocol is not gulty but more the display (array of WF graph Dbl)

It has started since I have put all my vis in the "Library" of my project.

Has somebody allready heard about this problem?

Thanks,

[jp_Braud]

Hi Lippoi,

Could you give us more precisions about your "special conditions" that could put your system in a bad state more than other times ?

This error could be due to a particular set of parameters... If you can, could you send us some small VIs that reproduce the problem ?

thanks for posting here,

[lippoi]

Hi,

I found the problem. Thanks anyway for your time.

The special procedure asked for a function of the scope to be initialized and to get the new waveform. My sub vi had a reference to an indicator to present the %work done on the main vi while the sub-vi was waiting for the new waveform to be collected. Actually this input was not connected in my main vi. When it is, LabView do no krash anymore.

Sincerely,

Lippoi