Same defadvice for: c-after-change jit-lock-after-change. I also activated this advice for semantic-idle-core-handler. Basically this was to catch one of them in the act of scrolling the buffer. However, I encountered the bug with these in place and none showed a window-start discrepancy.
If you have a reliable reproduction recipe, that would be very helpful.