https://bugs.documentfoundation.org/show_bug.cgi?id=151903
--- Comment #4 from Gabe <[email protected]> --- After further testing, I confirmed that the cause of the crash was actually due to having set up a for-next loop in which the high range of the loop was changing. The code includes removal of nodes via the loop. However, as each node was deleted the high end of the range was changing. Seems more likely to be an issue regarding for-next loops and not the node deletion as I thought. My fix was easy - simply stepping backwards in the for-next loop -- i.el, "for i = oParentNode.getChildCount-1 to 0 step -1". The issue of the system crashing rather than throwing an error message remains but I think is low priority. -- You are receiving this mail because: You are the assignee for the bug.
