https://bugs.winehq.org/show_bug.cgi?id=33814
--- Comment #28 from Steve Schnepp steve.schnepp@pwkf.org --- I'm also seeing that bug with a recent 8.0rc4 and
Vendor: Intel (0x8086) Device: Mesa Intel(R) HD Graphics 500 (APL 2) (0x5a85) Version: 20.3.5 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.6 Max compat profile version: 4.6 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2
A perf recording showed that most of the time is spend in wined3d_device_context_map, and indeed when I launch it with
WINEDEBUG="+fps,+timestamp,+pid,+d3d,+ddraw,+wgl,+opengl"
It seems that it is indeed many times in the same frame.
26138.298:0020:0024:trace:d3d:wined3d_resource_map resource 0A024060, sub_resource_idx 0, map_desc 0021E30C, box (62240, 0, 0)-(62400, 1, 1), flags > 26138.298:0020:0024:trace:d3d:wined3d_resource_map resource 0A024060, sub_resource_idx 0, map_desc 0021E30C, box (62400, 0, 0)-(62560, 1, 1), flags > 26138.298:0020:0024:trace:d3d:wined3d_resource_map resource 0A024060, sub_resource_idx 0, map_desc 0021E30C, box (62560, 0, 0)-(62720, 1, 1), flags > 26138.298:0020:0024:trace:d3d:wined3d_resource_map resource 0A024060, sub_resource_idx 0, map_desc 0021E30C, box (62720, 0, 0)-(62880, 1, 1), flags > 26138.298:0020:0024:trace:d3d:wined3d_resource_map resource 0A024060, sub_resource_idx 0, map_desc 0021E30C, box (62880, 0, 0)-(63040, 1, 1), flags > ...
So the function is called many times with some adjacent boxes.
Full log for a frame is attached as https://bugs.winehq.org/attachment.cgi?id=73923