Do you sometimes see this in your code while performing custom drawing using
1 2 3 4 5 6 7
And as always is very hard to track, because you cannot exactly say which draw command actually cause this or where does it comes from. But there is a simple solution to this:
Use this symbolic breakpoint
CGPostError in your xcode to stop executing on exact line where drawing error appears.
Now you can see all callstack and all values to find root cause of incorrect drawing.