ListView: section headers cause contentY + originY combination to be incorrect

I want to use a Flickable to scroll a ListView. For this I bind the contentY of the ListView to the contentY of the Flickable added to the ListView originY.

In the case of no section headers, this works perfectly. Scrolling the Flickable scrolls the ListView in sync.

However including section headers, when scrolling I get binding errors just at the moments when originY changes. As a result, the scrolling jitters at these moments.

I believe originY is not calculated correctly when section headers are used.

Attached is a test case which reproduces this. Just scroll the list to the bottom - when the ListView starts to delete/insert delegates, originY changes but jittery scrolling is seen (plus errors logged).

Commenting out the section header definition has everything working fine.

Note: I also see a crash when the list is scrolled rapidly. A bad workaround is to use a cachebuffer of reasonable size.