[Bug 42495] New: Rome: Total War mod Europa Barbarorum crashes in battles with CSMT
https://bugs.winehq.org/show_bug.cgi?id=42495 Bug ID: 42495 Summary: Rome: Total War mod Europa Barbarorum crashes in battles with CSMT Product: Wine-staging Version: 2.1 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aaronbpaden(a)gmail.com CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de, sebastian(a)fds-team.de Distribution: --- Created attachment 57366 --> https://bugs.winehq.org/attachment.cgi?id=57366 log with CSMT enabled With wine-staging 2.1 and CSMT enabled, Europa Barbarorum crashes when entering into a battle. Europa Barbarorum can be downloaded from here: http://www.moddb.com/mods/europa-barbarorum/downloads You need to install 1.1, then 1.2, and then unpack the fixes. Europa Barbarorum requires Rome: Total War 1.5 without the Barbarian Invasion or Alexander expansion packs. This prefix has quartz and wmp10 installed through winetricks, which I found to be necessary to get EB to work. In vanilla RTW, the battles do work with CSMT enabled. I can also confirm that the battles do work in EB when you disable CSMT. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42495 --- Comment #1 from Sebastian Lackner <sebastian(a)fds-team.de> --- Thanks for the bug report. Based on your log the application runs out of memory. My theory is that the game requires a lot of command stream blocks (used to transfer commands to the separate thread) when rendering complex scenes, and that it exceeds the available memory. To prevent that issue, we should probably limit the amount of blocks which are allocated for CSMT, or allocate smaller blocks to avoid wasting memory. Could you please monitor memory usage with and without CSMT to confirm this theory, and to ensure that the application doesn't leak memory over time. (For CSMT, it is expected that memory usage increases when rendering complex scenes.) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42495 --- Comment #2 from Aaron Paden <aaronbpaden(a)gmail.com> --- Created attachment 57372 --> https://bugs.winehq.org/attachment.cgi?id=57372 new log I think you're right about the memory thing. Firstly, it was a little harder to reproduce a crash this time than it was earlier, and when I did it crashed at the conclusion of a battle rather than at the start. I've added another log with a different set of errors from that session, and they're more unambiguously memory related. Still no crashes observed without CSMT. I recorded a peak of about 3.2GiB of main memory usage without CSMT and about 3.6 GiB with. A good chunk of that would have been used by GNOME and friends, though, and I actually have plenty more RAM to go. Could this be an issue with 32-bit prefixes, or an issue with VRAM? I only have 2 GiB of VRAM, but I don't know how to monitor VRAM usage. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42495 --- Comment #3 from Sebastian Lackner <sebastian(a)fds-team.de> --- I have pushed a patch to limit the CSMT memory usage more strictly. Please let me know if this fixes the issue. To test, you can either compile Wine Staging git (if it crashes, you might also need http://source.winehq.org/patches/data/130627, which fixes a regression in the dev branch), or wait until 2.3 is released. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42495 --- Comment #4 from Aaron Paden <aaronbpaden(a)gmail.com> --- Hi, sorry for the delay. I've tested this with wine-staging 2.3, and haven't been able to reproduce this bug, so it's probably been fixed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42495 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #5 from Sebastian Lackner <sebastian(a)fds-team.de> --- (In reply to Aaron Paden from comment #4)
Hi, sorry for the delay.
I've tested this with wine-staging 2.3, and haven't been able to reproduce this bug, so it's probably been fixed.
No worries and thanks for testing. Marking as fixed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=42495 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing Fixed Staging 3.14 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org