This occurs when you have 2 future sprints with issues, and drag the first sprint dragger to encompass all the issues of the second sprint as well as issues in the backlog. There were 4 issues in the second sprint, thus the 4 js errors. The end state left the backlog marker frozen at a position on the screen, see attached.