Please check older revision. There is nothing on ff81cf6d25609606c92be8b68b31e1bdbbced31e, and i dont think fc2e83e2425beb83aaf6c635733f374e4f616369 can create that bug (there is only a double call of SEQ_Render2D, instead of a single call, i dont think it can create your problem).