labview 2015 crash

[GokulGKM]

hi,

        i am using labview 2015.every 15min once.my program automatically closed than it will give crach report pop.

[MangeshD]

Hey Gokul,

Provide code that you aretrying to execute.

There could be thousands of ways LabVIEW can crash.

And as I can see its a LabVIEW 2014, isn't it?

[udka]

As LVK pointed clarify on which version of labview you are using 2015 or 2014.

-If it's periodic, i guess there might be memory leakage.

-Please check in Task manager if the memory is constantly increasing means there could be problem with the memory.

-Check all references closed, images disposed.

[GokulGKM]

hi,

      i am using labview 2015.i closed all reference and check task manager no memory leakage.whenour i move the mouse cursor in particular part in program it get crash.

i use in that place unset busy.vi.than i checked all in program set busy and unset busy.vi is properly open and closed.

[udka]

---

whenour i move the mouse cursor in particular part in program it get crash.

-What is there in that particular part?

[GokulGKM]

hi,

        mouse unset usy.vi used place(particular part).

[Bob_Schor]

There are three likely possibilities -- (a) you did something "wrong" in your code, (b) you have a faulty LabVIEW installation or environment, or (c) you have found a (fairly rare) Fatal Flaw in LabVIEW.  So far, we have not seen any code, and have not had the opportunity to test your code in our environment, allowing us to help evaluate possibilities (a) and (b).  Possibility (c) is the least likely.

If you want and need our help, then you should absolutely post your code.  If you follow good LabVIEW Development practices, and have a LabVIEW Project with numerous sub-VIs that all work together, compress the folder containing the Project and attach the resulting Zip file.  If, on the other hand, everything is in one VI, attach that.  We'll examine the code and test what we can -- maybe, seeing the code, we can isolate the problem.  Without it, we're reduced to "guessing" ...

Bob Schor

[udka]

As Bob pointed without code it is very difficult to identify what went wrong.

If you cannot post code, try debugging with Desktop execution trace toolkit and see what is happening! http://www.ni.com/white-paper/8083/en/

[Bob_Schor]

As a P.S. to my previous post about a possible "mis-installation" of LabVIEW, while answering another Post on this Forum, I happened to discover that my main Work PC, where I do most of my LabVIEW Development, and which contains LabVIEW 2012 (SP1), 2014 (SP1), 2015 (SP1), and 2016, has some "mis-installation" somewhere (I've been successfully developing in LabVIEW 2016, but found that MAX wasn't handling some of my devices properly).

I've just gone into Control Panel and said to "Remove All" NI Software, a process that will take something like an hour or two (there are 1484 products to remove, and it has done 40 so far ...).  So even if you are somewhat experienced, it is possible to "mess up" ...

Fortunately, I think I have a working LabVIEW 2016 VM ...

Bob Schor