apitrace/apitrace — Issue #64: qapitrace memory usage explodes after replaying trace
Author: vpelletier
Created: 2012-01-21 09:18:39+00:00
State: open

I traced a game ("Two Worlds", available from GOG, ran on linux using wine), which generated a 1GB trace file.
It can load without a problem in qapitrace (memory usage doesn't exceed 150MB after loading).
I can lookup a few individual states with success, and memory usage going up a bit after each lookup (I guess that's just the result of displaying state details).

But after replaying the whole trace, memory usage increases regularly until I kill qapitrace.
I guess is qapitrace filling state details asynchronously from replay end/in parallel to replay, and end up using too much memory. I guess a workaround would be to allow disabling this, if my supposition is correct.