07-07-2010 02:14 PM
I am using LV 2009 SP1 and have been working for several days and nights on an XML parser.
The code uses lots of recursive algorithms and everything was tested yesterday and worked OK.
Continued the work today, all code from yesterday still ran up until a point in time (no id why) it just stopped, LV hangs and then momentarely crashes.
Restart LV, open code, run an XML related VI and crashes again...
When LV crashes, its CPU usage is about 0% and memory usage about 128Mb RAM (default) so nothing out of the ordinary there.
It seems that the LV XML parser is dead? I tried to pinpoint the source of the crash, but everytime I think "this must be it" by isolate a portion of the code, something else crashes - but always XML related.
I was glad to see the work progressing and now I've come to a stop point.
I am now "repairing" LV through add/remove programs console. No idea if this will do anything.
I must say that I have LV8.6.1 and LV2009SP1 installed together. I open only one LV version at a time and for this project, I am running LV2009 since last week. Not once I started LV 8.6.1 during that time and I did not had any problems with my code up until now. I also copied the contents of some VI's to new VI's and saved them again (perhaps the VI was corrupted due to the crash), but that did not help at all. I also rebooted the PC but nope, LV keeps crashing. Other code still runs, but XML related VI's have the tendency and especially the recursive programmed XML VI's crash. Could it perhaps be the VI-server? Come to think of it: to program a VI recursively, you need to do a recursive callback via the VI-server. Maybe the error is located there?
suggestions, ideas, anything: very welcome!
Solved! Go to Solution.
07-08-2010 02:30 AM
07-08-2010 02:35 AM
Thanks!
Yesterday night I solved the problem, and indeed the other topic you mentioned is correct. It was in fact a premature closure of the DOM reference that triggered LV to crash. Very cumbersome to debug since I am using it in a recursive algorithm but I managed to locate the error.
Reinstalled LV, but it kept on crashing so I was pretty sure it was due to my coding 🙂
I must remember myself from time to time that all errors are human...
Glad to see that I am not the only one facing these problems so thanks again Muks!!