Steps to reproduce bug

Using the attached example project in test.tar.xz:

1. Use the mouse to flick the list upwards (i.e. the list scrolls towards increasing indices).  The list should be flicked with sufficient speed to have it scroll for a good amount of time.
2. While the list is moving, press the "Go to end" button.
3. The application will freeze.

While the application is frozen, memory usage rapidly increases.  I do not know if the application eventually recovers (didn't want to risk the OOM killer).

I've noticed similar behavior when flicking downwards (i.e. towards decreasing indices) and calling positionViewAtBeginning.  I've been able to reproduce this behavior on 5.11.0, 5.11.2, and 5.12.0 alpha.

Expected behavior

The application should move the list to the bottom-most row.

Workaround

Stopping flicking (i.e. calling Flickable.cancelFlick) before calling positionViewAtEnd seems to work around the issue.