Stuck pixel scan identifying almost 100% of SYNC as stuck

It seems the stuck pixel scan currently identifies almost the full SYNC FE as stuck, independent of the threshold setting. Is this a bug or a known "feature" of the front-end? In this case we should make sure, the scan is not run (or at least not disabling pixels) on the SYNC FE...