https://bugs.winehq.org/show_bug.cgi?id=45369
--- Comment #12 from roman@hargrave.info roman@hargrave.info --- (In reply to Zebediah Figura from comment #11)
Well, I wouldn't grab logs while Steam is updating itself if possible.
Still, if it's that infeasible, I guess just +seh,+module,+explorer might be enough to rootcause the problem.
The updater runs and may or may not unpack files every startup. Regardless, the fact that it was doing what it was to the updater means that I would have to clock about three hours of gameplay (measured at full speed) at roughly ten seconds per frame, which would be totally not feasible. Still, nonetheless, I have attached a log with -all,+seh:trace,+win:warn,+explorer:info,+module:warn (or something, the ensuing process leak actually killed my disk IO in less than three seconds due to the kernel attempting to swap 16Gb of resident programs at high priority, I don't have the exact invocation since my shell actually failed to write a history file as a result)