Deus Ex Human Revolution runs out of resources after a while

[mtmkls]

The game renders correctly (in DX9 mode), and runs much better than with wined3d. However, after an hour or so (depends on how many different areas are visited) the game quits with this dialog:

Clicking OK takes me to the graphics setup dialog that normally only shows up when starting the game the first time. From there the OK button would restart the game, but it immediately bails out with the same error.

[axeldavy]

is it taking more and more cpu ram as well ? How many gpu ram do you have ?

[mtmkls]

I have 2GB VRAM, but DXHR doesn't use more than 800MB VRAM and 180MB GTT. Its RAM usage is more suspicious: 650MB RES, 4080MB VIRT. Maybe it runs out of address space?
When it is close to crashing usually this is printed to the console a few times:
radeon: mmap failed, errno: 12

[axeldavy]

does it increase only at scene change, or all the time ?

[mtmkls]

These numbers are more-or-less constant. I see no increase.

[axeldavy]

Could you take a small log where you would load a save just before a scene change, trigger the scene change, then exit (best by killing the program) ?

To get a log you have to use NINE_DEBUG=all your_program &> yourlogfile
No log is produced unless mesa is built with --enable-debug

[mtmkls]

The problem is not directly triggered by level transitions. When walking around in a hub area stuff gets loaded and unloaded dynamically, and eventually mmap fails, but the overall memory usage stays about the same. Anyway, I captured a debug log (load latest autosave, start in the Chiron building, turn around, exit to the Detroit hub area, ctrl-c). I had to rename it because bz2 is not allowed.
dxhr_nine.log.bz2.zip

I noticed that when the game exits to the settings dialog due to the error, and I select a lower resolution, the game can continue where it was, but eventually it exits again.

[axeldavy]

thanks for the log.
I failed to see exactly what is the cause of the problem though.
Is the problem still happening with:
. Mesa 13 or older
. csmt_force=0

[axeldavy]

Have you tried setting the large address aware flag on the game exe ? (tools are available on internet for that). Apparently wine with gallium nine uses a bit more address space and games which are tight can crash. With the Large Address Aware flag, more virtual memory is available to the application.