Comment 10 for bug 195843

If INTEL_BATCH enables greater concurrency, bugs can be really difficult to be traced. We will probably never have a deadlock in 99% of cases, but some unlucky guy with a specific configuration, or us in 1% cases, will experience deadlocks under compiz, without being able to tell if this was compiz or INTEL_BATCH fault. Replicating the conditions of concurrency problems is a difficult problem.

For example, compiz sometimes hangs, if for some reason the animation lasts too long (e.g. if I use the shift switcher plugin under heavy CPU load). This is not due to INTEL_BATCH (I had this problem before) but seems a symptom of a concurrency problem. So, even if I am currently happy with INTEL_BATCH, and was among those who asked to make it default, I am happy that it is left off for Hardy, and until upstream enables it.