Then fix that weird "image jumping" issue. That's a warning sign for some deep code issue, overwriting memory or faulty pointers and such.

I've once written a program (or... 10+ programs) to solve a 16x16 tile puzzle called Eternity II. I've experienced some weird bugs doing so, for example the program going through the board in a weird and seemingly not programmed way/ routine after ~100 iterations. All bugs where either memory related (wrong array index access) or - what I didn't know back then - limited stack memory size. I called a recursive function which used local arrays, like data[1024], not knowing that the allocation of such "big" arrays fails after some levels into the recursion.