LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

memory and performance crashing 8.2.1

Hi there,

On both macOS and window XP the memory and perfomance profiler crashes the complee LV Dev Environment instantly
once the start button is click.  I update to LV8.2.1f4 same thing.

Also recently, after more than 5 years developing my application and in use during this period, 24 hours per day, with uptimes of 1- 2 months,  now after a certain number of measurement interations it crashes ( window xp  aplology meassage - ).
The WinXP event viewer states that my LV app crashed in a third party ActiveX module.
The ActiveX component has been used unchanged for more than 2 years so I doubt it is the problem, unless some window/lv update has caused it to hang.

I have carefully examined my code for nto closing refs and file pointers and notification quese that never get emptied/read
and i believe there are none, but of course i can never rule that out, but it is very minimal likely hood.

if i watch the memory use of the application in Windows Task manger i do see the memery increase very slowly, but that could also be just more data accumalating - althohg it is not stored in arrays but immediatly to file.

Any thoughts welcome.

michael proctor
Stanford University


0 Kudos
Message 1 of 2
(2,428 Views)

Michael,

When LabVIEW crashes from running the performance and memory profiler, do you get the CPP error dialog the next time you start LabVIEW?  If so, I would suggest submitting an error report with it.  This will send us the error log file and help us determine what may have happened.

As for your application, you say this has not been changed and was running for five years, correct?  Has anything else changed on the computer?  Did you recently add new software to the system? 

How long does it take before the program crashes?  Is the time it takes reproduceable?  How long have you been seeing this behavior?  Did the crashes just suddenly start? 

In certain cases, shared resource conflicts or corrupt files could cause problems like this.  For XP, this can often be solved by doing a system restore to the time before the crashes started happening.

Regards,

Craig D
Applications Engineer
National Instruments

0 Kudos
Message 2 of 2
(2,402 Views)