Use of uninitialized memory during TestSetGet.tcl
This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
The test TestSetGet.tcl is unreliable because it does not correctly initialize objects before using them leading to access and use of uninitialized memory.
These issues seem for the most part related to use of uninitialized bounds in datasets, bounding boxes, actors etc.
The attached valgrind log file illustrates the issue.
Either the test needs to more careful about initializing objects before using them or the objects need to initialize themselves better or detect uninitialized use and prevent themselves from using uninitialized memory.