Fatal Internal Error:"memory.cpp",line593

[Nutronik]

This error message comes up rather seldom, but it will stop our data acquisition process and data will be lost.
This failure came up also with Labview 6.0.
With 7.0 it happens less frequently but dit not disapear.
What can I do ?

[Jonnie_5]

This may be related to a memory leak from a Delete from array:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c8eb44cece4bcd5d86256afd004b2027?OpenDocument

It could also be related to a DLL:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/da7fa9c467ba4cc886256e62006deba2?OpenDocument

For general internal error troubleshooting, see:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/01b186b5ceb1d07786256747000f4319?OpenDocument

[Nutronik]

The first link was quit interesting.
Question:
is
....memory.cpp, line 563
the same as
....memory.cpp, line 593

[rolfk]

Nutronik wrote:

> The first link was quit interesting.
> Question:
> is
> ...memory.cpp, line 563
> the same as
> ...memory.cpp, line 593

If it is from different LabVIEW versions, that is quite likely.
Otherwise it may be of similar reason but not exactly the same.

Rolf Kalbermatter

[peterguy]

Hi Nutronik,

this Error normally indicates a memory access violation, typically caused by an array handle.

In order to investigate your error I would like to ask you to post your VI, so that I can have a look at it.

Could you also please tell me, which DAQ-card you are using?

regards,

Peter Weber
NI Germany

[Nutronik]

Hi Peter,
thanks for your comment.
There is no DAQ-card involved.
We use a MXI-VXI Subsystem for our data acquisition.
Unfortunately I can not localize the error. There are many VIs in use. A lot of them make use of the the "replace array subset" function. Labview doesn't report the VI's name. The applictation is created with the Application builder. I could not catch the error with the LV development environment.
Regards
Gerhard Finger
Nutronik GmbH

[peterguy]

Hi Gerhard,

I found an entry in our knowledgebase that should help you to localize the Error. Here it is:

http://digital.ni.com/public.nsf/websearch/01B186B5CEB1D07786256747000F4319?OpenDocument

Regards,

Peter Weber
NI Germany