LabVIEW Class crash - ntdll.dll access violation

Question

Hi,
When I close my LV11SP1f2 I always get a warning.
It didn't bother me until a vi I wrote that uses a class with nothing out of the ordinary started crashing my LV.
The crash says that: "DAbort 0x37C03D in MemoryManager.cpp"
I sent the log files to the local support and they saw that the common issue between my logs is an access violation in ntdll.dll.
Any operation that uses the property nodes of that crazy class fails, sometimes with a crash and sometimes with a error that sends me to a bundle by name in the autocreated property node.
I rewrote the project with the class and there is no error.
Sending the crashing project to another computer gave no error.
Before I go on and investigate windbg to search for a conflicting app and finally formatting my entire computer could some1 help? Please...
I attached several logs for example.
Thanks in advance,
GoofyWires.
Attachments:
92c82e7b-fa2a-43af-b2be-a6650c031681.zip ‏2485 KB
daa462b5-9395-4e3f-8894-05a3bdb3d159.zip ‏65 KB
ea2c40ef-056d-41ed-a4c5-9cf4bc6666fc.zip ‏494 KB

Answer 1

I did a clean format and reinstalled LabVIEW 11.0.1f2 without adding many of the add-ons from VIPM and without installing the rest of my shortwave, yet, the crash is still here!
I was able to reproduce it on my pc:
1. I have a class that contains two children of another class which each contain another class with a class inside it.
2. I accessed the classed through property nodes.
3. I then went on and deleted a private data from the first class control, deleted its property nodes and added a new private data to that class control and added the property nodes for it.
4. I updated the vi that used the classes to stop using the deprecated property node and start working with the new one.
5. I did a "save all" and run the vi. All OK!
6. I closed LabVIEW and reopened the project and run the vi which is not broken! LabVIEW crashes!!!
I guess the complexity of the class is not the issue and it can be reproduced in a much simpler way.
Yet, since I bet the scenario caused you to raise an eye brow I'll give an example as an analogy:
File Handler class contains ASCII Read class and ASCII Write class which inherit from class ASCII.
Class ASCII parent contains class Headers while class Header contains class Data.
Thus, class ASCII Handler will use class ASCII Read/Write to give a high level simple interface while during the read/write the inner ASCII Read, for example, will add to the Header class in it the read data which will in turn be added to the array in the private data of class Data.
I'll try and reproduce it on a different pc and send the local NI support the code and way to reproduce.
I see two possibilities:
1. Something is wrong with my new Dell PC.
2. LabVIEW doesn't handle and propagate correctly changes in a class to all the vis that use it. Maybe changing the array size in a class overrides some memory since the class can't change its size.
Please let me know if this rings a bell.
Update: I coundn't reproduce the crash on my pc with a simpler case. There is something missing...
I'll try to replroduce with the complex class on a different pc and if it crashes I'll simply send my original code.