[Bug 41614] New: Star Wars Galactic Battlegrounds crashes and wine gives me an " unhandled page fault on write access" error
https://bugs.winehq.org/show_bug.cgi?id=41614 Bug ID: 41614 Summary: Star Wars Galactic Battlegrounds crashes and wine gives me an "unhandled page fault on write access" error Product: Wine Version: 1.9.21 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ipenguin(a)gmail.com Created attachment 55964 --> https://bugs.winehq.org/attachment.cgi?id=55964 Terminal output at time of crash Tried to play multiplayer SWGB 1.1 through Voobly. My friend has the same Wine version and game version installed as I do, and his version works fine. When we play multiplayer, my game crashes every time, usually within 3-5 mins. I get an error popup: "The program battlegrounds_x1.exe has encoutnered a serious problem and needs to close. We are sorry for the inconvenience." The wine error readout from the terminal from approximately the time the game starts is attached. My friend whose game did not freeze got most of the same errors in Wine, but the error I got that he didn't is: wine: Unhandled page fault on write access to 0x8b11762d at address 0x401c3e (thread 008b), starting debugger... Any ideas what could be causing this? -- 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=41614 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #1 from winetest(a)luukku.com --- Does your friend have mac too? Don't see anything interesting at the log. -- 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=41614 --- Comment #2 from ipenguin(a)gmail.com --- (In reply to winetest from comment #1)
Does your friend have mac too? Don't see anything interesting at the log.
Yes, we both do. He's on 10.9.x though and I'm on El Capitan. Not sure if that would make a difference. Otherwise we followed the exact same steps. The unhandled page fault error isn't a concern? It seems like that's probably a good place to start, since that's the only part of the error message I got that he didn't. -- 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=41614 Jeff Zaroyko <jeffz(a)jeffz.name> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal -- 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=41614 --- Comment #3 from winetest(a)luukku.com ---
The unhandled page fault error isn't a concern? It seems like that's probably a good place to start, since that's the only part of the error message I got that he didn't.
Well yes but you need to use some debug channels to get the crash location. I think +tid, +relay is what they use. And log into a file and compress the file. The output can be gigabytes easily without compress. Then someone needs to analyze it and make a patch. It's not that easy. -- 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=41614 --- Comment #4 from ipenguin(a)gmail.com --- Gotcha, I see. Is that something I can do from the wine terminal? What would be the process for running that debug? (In reply to winetest from comment #3)
The unhandled page fault error isn't a concern? It seems like that's probably a good place to start, since that's the only part of the error message I got that he didn't.
Well yes but you need to use some debug channels to get the crash location. I think +tid, +relay is what they use. And log into a file and compress the file. The output can be gigabytes easily without compress. Then someone needs to analyze it and make a patch. It's not that easy.
-- 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=41614 --- Comment #5 from winetest(a)luukku.com --- Start reading from https://wiki.winehq.org/Debug_Channels https://www.winehq.org/docs/winedev-guide/wine-debugger -- 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=41614 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #6 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with plain wine-7.0-rc3? -- 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 (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla