@Brent Sorrentino
I’m always updated. Now I’m using the last one (Version 2017.3032 (2017.2.7)).
Its not resolved. Always occur when scrolling up very slowly and moving the fingers in a little distance (kinda 0,5 cm).
I’ve looked at all the videos and it is a reproducible error. This may have gotten lost while switching to our new ticketing system. I have re-filled Ed’s bug report from the other thread and escalated it. Here is the new case ID:
7921379
In my testing I can only get it to crash after I’ve pinned a category to the top and then scrolled it back down a little bit until I have a row barely visible and then scroll it from that row and it hits the run time error.
Rob
I just tried it in the current public release and it still did it, so either I wasn’t doing a very good job of trying to reproduce it when I said that or something very odd has happened and it’s become unfixed between then and now.
@Rob Miracle, you need to have more than one row off the top of the tableview, scroll one to just barely visible then press on it long enough for it to change colour then drag down off of it to uncolour it.
Assuming it’s the same problem (line numbers have changed so clearly some work has been done on tableviews) it’s not checking whether the row above the selected one has been culled before it reshows the separator line at the bottom of it.
It’s already in an Engineer’s hands.
Rob
I know it was fixed. I’m trying to verify the changes got pushed out in a daily build.
This should be resolved in daily build 3040.
Rob
Yeyyyyy! 
Still not working on 3040 
We are looking into it.
Rob
That was an oops on our part. Without getting into too much detail, widgets are in their own source control repository and have to be merged into the main repo and somehow this fix didn’t get merged properly.
This should be in the next daily build.
Rob