Probably as it is a memory error.
The attached patch corrects the crashy behavior by (I think) placing the correct amount of memory on the heap to avoid dereferencing a bad location when checking the LIB_ID. However, it doesn't fix the underlying memory leak in the component tree.
Probably as it is a memory error.
The attached patch corrects the crashy behavior by (I think) placing the correct amount of memory on the heap to avoid dereferencing a bad location when checking the LIB_ID. However, it doesn't fix the underlying memory leak in the component tree.