apitrace trim misbehaviour

[Andre Heider]

Hi there,

apitrace trim told me to write this ;)

On the trace (~260MiB) at:
http://static.hackmii.com/dhewg/brutalz.trace.xz

I tried to trim it down for a bug report to the problematic frames:
apitrace trim --frames=1150-1683 -o trim.trace brutalz.trace

That took >2.5h at 100% load on tmpfs on a i5-3570K and gave me a
trace that fails to replay.

Using apitrace head 0227203a229e85f98a491c6b9480c0.

Thanks,
Andre