Removing a string control from a Strict Type Def Cluster caused LV2010 SP1 to crash

[Ray.R]

Has anyone else seen this?

The crash does not give any error message, code or anything.  When re-starting LabVIEW, it does offer to restore the unsaved vis.

This originally occurred with LabVIEW 2010 (once or twice on this ctrl).  I hoped that the upgrade to SP1 would cure this, but it did not. 

The steps are very simple...  I have an existing Strict Type Definition which contains 11 string controls, 4 numeric controls, and 1 boolean.  Nothing special.  When I try to delete one of the string controls, LabVIEW simplyt dissappears from the screen..  A rather violent crash..

I tried it again and it was fine, as I would have expected..  Applied the changes and it was fine.

I am not calling this a bug, I simply want to see if others will report this behavior in case there is something to investigate with this version.

[Drew_T]

Ray,

I am sorry to hear you have experienced this.  I have not experienced this behavior, and was unable to reproduce based on the directions you have provided.  

As far as investigating this error goes, I would first check to see if a crash log was generated in \My Documents\LabVIEW Data\lvfailurelog

If there is no log present for the issue you are describing, you can also troubleshoot using the directions contained in this KnowledgeBase article:

http://digital.ni.com/public.nsf/allkb/4DFF0C6364BDBFA8862575F6005C3A48?OpenDocument

While the forums can be a great place to share knowledge and communicate with others that have experienced similar issues, if you would like to troubleshoot this crash directly with an NI Applications Engineer, and you have a Standard Service Program contract, feel free to get in touch with us by visiting ni.com/support and clicking the Phone an Engineer or Email an Engineer links.

[altenbach]

Ray, just curious. When you delete that contol, do you just have the Typedef open in the control editor or do you also have complocated VIs or projects open that currently use that typedef.

[Ray.R]

---

@drew T wrote:

Ray,

I am sorry to hear you have experienced this.  I have not experienced this behavior, and was unable to reproduce based on the directions you have provided.  

As far as investigating this error goes, I would first check to see if a crash log was generated in \My Documents\LabVIEW Data\lvfailurelog

If there is no log present for the issue you are describing, you can also troubleshoot using the directions contained in this KnowledgeBase article:

http://digital.ni.com/public.nsf/allkb/4DFF0C6364BDBFA8862575F6005C3A48?OpenDocument

While the forums can be a great place to share knowledge and communicate with others that have experienced similar issues, if you would like to troubleshoot this crash directly with an NI Applications Engineer, and you have a Standard Service Program contract, feel free to get in touch with us by visiting ni.com/support and clicking the Phone an Engineer or Email an Engineer links.

---

Hi Drew,

I checked and there were no failure logs for this error.  Only some older one, unrelated.  I will look at the link you provided.  It's low priority for me at the moment since the project is now fine. I was mostly curious if other had experienced something similar.

---

@altenbach wrote:
Ray, just curious. When you delete that contol, do you just have the Typedef open in the control editor or do you also have complocated VIs or projects open that currently use that typedef.

---

Christian,

Your "spidey" senses must be tingling.  😄

I had the project open, along with a number of VI's (public class - same class and public class - members of other classes) opened at the time.  I actually was tracing an error, which meant opening VI's and working my way up the the VI containing this Typedef control and then right clicking the control to "Open Type Def". 

The typedef opened without a problem.  I had already visited this typedef before and previously removed 2 other string controls from the cluster.  I may have encountered a crash previously at that time.  And if my memory serves me correctly, I had also opened a number of VI's in a similar fashion.  I did not pay attention to this detail since opening many VI's at once is a normal part of my life.  🙂  I can't remember how many VI's were opened at the time, but it could have been close to 10... maybe more..  Using LVOOP.

Can you share anything?

[altenbach]

---

@Ray.R wrote:
Your "spidey" senses must be tingling.  :D

---

No spidey senses... I was just worried that you original description was probably insufficient to demonstrate the problem. Can you get it to crash if you only open the typdef in the control editor and then delete the item as described? If so, can you attach the control so we can try too?

[Ray.R]

I sucessfully removed the last string control from the Typedef cluster.  I think you are correct that the successful attempt was done while only that control was open. 

Unfortunately, I cannot post the control in question.  What I can do is a modified version of the same and post that one.  I do have access to an original version (not at the moment - different customer site),  I will duplicate / modify and then post the typedef.

I have been modifying the code (project) since and there was no subsequent crash. 

EDIT SECTION:

I should mention that I did not attempt to investigate the crash by attempting different scenarios that would cause a crash.  Unfortunately, working 60 - 80 hrs/week leaves me little time to investigate. (fortunately, I take the time for a little refuge here at the forum while enjoying a snack with a warm tea 😉 )