LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

memory couldn't be read

when I am running my program I have the following message.see attachement.
How to solve this issue?
0 Kudos
Message 1 of 3
(2,570 Views)

@beni wrote:
when I am running my program I have the following message.see attachement.
How to solve this issue?




Investigate where you use Call Library Nodes in your app. Then carefully examine all of them to use the correct parameters and buffer sizes.

Rolf Kalbermatter

Message Edited by rolfk on 06-21-2005 08:27 AM

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 2 of 3
(2,565 Views)
This can also be a memory leak due to unclosed references to LV objects in the code.

I got this sometimes from a sub-VI of mine which made extensive use of LV object references.

DLLs and CINs are also very likely (perhaps more likely) candidates.

Hope this helps

Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)
0 Kudos
Message 3 of 3
(2,560 Views)