LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

MemoryManager.cpp

Hello all,

 

I have recently experienced a problem, that never have been before until now, and i don't know what i can do to solve this problem.

 

I have a program were we use it on several machines, since labview 7.0 , offcourse the program has been changed, but for example this last version we have it on several machines. We use LabView 14 sp1 on win7, 8.1 or 10.

 

Two weeks, in one client the program crash with the follow error : MemoryManager.cpp - 0xF50EFD7B.

This error in two week occurs 4 times, 2 on the same computer and other 2 in two different computers, and in one of them it was with a different program.

 

I Use Labview 2014sp1 run time f3, Ni-Daqmx 14.2, Ni-Imaq 14.5.0, Ni-Imaqdx and Ni-Visa Runt time 14.0.1.

 

This situation gradually is becoming a serious problem, what i can do???

 

I take a picture and i put it in annex.

 

Sem Título.png

 

 

0 Kudos
Message 1 of 5
(4,150 Views)

That may be due to running out of memory.

 

If you think is was working OK previously, are you running for longer periods of time?

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 5
(4,146 Views)

What changes did you make between the version that works and the version that crashes? Can you post your code?

Have you tried running the desktop execution trace toolkit to look for reference leaks? Does the problem occur straight away, or after it has been running for a while? Does the programs memory usage grow over time? Do you call any external code (e.g. DLLs)?

(I'm thinking along the lines of a memory leak or a reference leak (e.g. opening and not closing references))


LabVIEW Champion, CLA, CLED, CTD
(blog)
0 Kudos
Message 3 of 5
(4,144 Views)

Thanks for your help,

 

I have this program working in other clients for a few time and never pop up any error.

 

No, i didn't use the desktop execution trace toolkit to look for reference leaks, to be sincer i thought that i can't use this with Executables.

 

The strange is the program is capable to run several days working withtout any crash.

0 Kudos
Message 4 of 5
(4,126 Views)

Monitor the memory usage over a long time. If ti contnues to increase it will eventually fail.

 

Ben

 

 

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 5 of 5
(4,111 Views)