A cycle time violation happens when the tasks in a cyclic task class overrun the cycle time plus tolerance. This function may be the cause, but it may also be the case that the function is taking a reasonable amount of time but doesn’t have enough time left to complete once it starts. In other words, a cycle time violation is often caused by a combination of factors even though the log entry indicates a specific line.
It’s generally a good practice to spread your programs across multiple task classes as opposed to having them all in one. This lets you set priorities and run tasks that take longer in a slower task class. At the very least, you could try spreading your tasks out across 2 different 12ms task classes and see if that changes the result.
If you want more information about how long each of your tasks takes to execute, you can use the Profiler via Open→Profiler in Automation Studio.