ListView segmentation fault when setting highlight to null

In certain circumstances setting ListView's highlight property to null can cause a segmentation fault. The attached application can be used to reproduce the issue. See also the attached callstack.txt.

In the application the highlight property is set to null when active focus is lost. Because of this there's a problem in QGraphicsItemPrivate::setVisibleHelper in this loop:

    // Update children with explicitly = false.
    const bool updateChildren = update && !(flags & QGraphicsItem::ItemClipsChildrenToShape);
    foreach (QGraphicsItem *child, children) {
        if (!newVisible || !child->d_ptr->explicitlyHidden)
            child->d_ptr->setVisibleHelper(newVisible, false, updateChildren);
    }

It seems the iterated QList is modified and deep copied during the loop due to a child getting deleted. After this the QList copy contains a null pointer which causes the fault.