http://bugs.winehq.org/show_bug.cgi?id=32302
Bug #: 32302 Summary: Endless Space >=1.0.25: crash during advanced game Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jitsumi@gmail.com Classification: Unclassified
Created attachment 42640 --> http://bugs.winehq.org/attachment.cgi?id=42640 Wine log of the crash
The game crash after a while. I don't know what make it crash, but it is not random, when I load my autosave, the game crash exactly at the same moment every time.
I attached the wine log, and the memory dump.
I m available for debugging.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #1 from jitsumi@gmail.com 2012-11-27 01:37:23 CST --- Created attachment 42641 --> http://bugs.winehq.org/attachment.cgi?id=42641 Memory dump of the crash
http://bugs.winehq.org/show_bug.cgi?id=32302
jitsumi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jitsumi@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32302
jitsumi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.5.18
http://bugs.winehq.org/show_bug.cgi?id=32302
Aleksei Gusev aleksei.gusev@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aleksei.gusev@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #2 from Aleksei Gusev aleksei.gusev@gmail.com 2012-11-27 02:45:40 CST --- I have the same issue and I also can provide any help the developers request.
Maybe there is some wine patch worth to try to apply? Unfortunately, my qualification is not enough to fix the bug, but I can patch and compile wine, just in case.
Thanks in advance!
http://bugs.winehq.org/show_bug.cgi?id=32302
Dima mondoc@pochta.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mondoc@pochta.ru
--- Comment #3 from Dima mondoc@pochta.ru 2012-11-27 03:42:10 CST --- ( R- -- I - - - ) in memory dump, yeah i have this one too. But mine was RIP, so it doubted me greatly.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #4 from Dima mondoc@pochta.ru 2012-11-27 03:45:05 CST --- As far, as i understand, i have the same bug. Game crashes and there is «RIP» with lots of dashes in dump.
http://bugs.winehq.org/show_bug.cgi?id=32302
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |00cpxxx@gmail.com
--- Comment #5 from Bruno Jesus 00cpxxx@gmail.com 2012-11-27 09:44:51 CST --- Looks like a dupe of bug 31336. The crash is the same even with the different game version.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #6 from jitsumi@gmail.com 2012-12-03 02:14:12 CST --- Yes, I was not sure if it was the same bug or not, that is whay I asked to close the other post.
I got an idea when I was speaking with people from the official forum. When the game crash, there is more than 2GB of virtual memory allocated to it.
So, I know there is a limitation of the amount of memory that a 32 bits application can use. It is generally 2GB. I know that with some trips it is possible to go to 3GB of memory, but I do not know how wine manages all these.
But, is it possible that wine tries to allocate more memories that the application can use? That may explain the "Unhandled page fault on read access", right?
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #7 from voidcastr voidcastr@gmail.com 2012-12-07 05:19:33 CST --- Created attachment 42736 --> http://bugs.winehq.org/attachment.cgi?id=42736 backtrace with debug symbols
Here's a better backtrace with wine debug symbols, created using the current wine git (wine-1.5.18-294-g9b90ea5).
http://bugs.winehq.org/show_bug.cgi?id=32302
voidcastr voidcastr@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |voidcastr@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #8 from voidcastr voidcastr@gmail.com 2012-12-07 05:50:11 CST --- Btw, in the case from which I obtained the above backtrace, the crash occurs at a memory consumption of ~783 MB. Hence, I suppose this being the cause is rather unlikely.
I think we should focus on this section of the backtrace instead:
15 0x7b864b58 call_process_entry+0xb() in kernel32 (0x0032fe58) 16 0x7b864c9e start_process+0x143(peb=0x7ffdf000) [/wine/dlls/kernel32/process.c:1083] in kernel32 (0x0032fea8) 17 0x7bc81754 call_thread_func_wrapper+0xb() in ntdll (0x0032feb8) 18 0x7bc817a3 call_thread_func+0x44(entry=0x7b864b5a, arg=0x7ffdf000, frame=0x32ffb8) [/wine/dlls/ntdll/signal_i386.c:2522] in ntdll (0x0032ff98) 19 0x7bc81732 call_thread_entry_point+0x11() in ntdll (0x0032ffb8) 20 0x7bc5507f start_process+0x25(kernel_start=0x7b864b5a) [/wine/dlls/ntdll/loader.c:2653] in ntdll (0x0032ffe8) 21 0xf763ee15 wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) 22 0xf763edf3 wine_switch_to_stack+0x2a(func=0x7bc55059, arg=0x7b864b5a, stack=0x330000) [/wine/libs/wine/port.c:59] in libwine.so.1 (0xffff7b68) 23 0x7bc553c1 LdrInitializeThunk+0x341(kernel_start=0x7b864b5a, unknown2=0, unknown3=0, unknown4=0) [/wine/dlls/ntdll/loader.c:2709] in ntdll (0xffff7be8) 24 0x7b865577 __wine_kernel_init+0x71b() [/wine/dlls/kernel32/process.c:1255] in kernel32 (0xffff8a78) 25 0x7bc55b56 __wine_process_init+0x156() [/wine/dlls/ntdll/loader.c:2918] in ntdll (0xffff8ac8) 26 0xf763d642 wine_init+0x13d(argc=0x2, argv=0xffff8fe4, error="", error_size=0x400) [/wine/libs/wine/loader.c:831] in libwine.so.1 (0xffff8b08) 27 0x7bf011aa main+0x13d(argc=0x2, argv=0xffff8fe4) [/wine/loader/main.c:237] in <wine-loader> (0xffff8f48) 28 0xf746f4d3 __libc_start_main+0xf2() in libc.so.6 (0x00000000)
I already took a look into the code (i.e. process.c), but at the time writing this I have absolutely no idea what's going on in there.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #9 from voidcastr voidcastr@gmail.com 2012-12-07 06:42:44 CST --- Actually, this could also be a problem with the mono version which is shipped with the game and which can be found in ".../Endless Space/EndlessSpace_Data/Mono/". It's mentioned in the stack trace. But since we have no debug information (i.e. symbols) for that one, I don't think chances are that we can narrow down the causes of the crash from this point.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #10 from voidcastr voidcastr@gmail.com 2012-12-10 17:27:23 CST --- Starting the game with
MONO_DEBUG=explicit-null-checks wine EndlessSpace.exe
seems to solve the problem for me -- at least for one of my autosaves. However, I did not play a new game right from the start yet (insufficient spare time).
Can anybody confirm?
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #11 from jitsumi@gmail.com 2012-12-11 01:58:35 CST --- It's working well for me ^^ Good job. So, it's a bug in Mono???
http://bugs.winehq.org/show_bug.cgi?id=32302
jitsumi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.5.18 |1.5.19
http://bugs.winehq.org/show_bug.cgi?id=32302
jitsumi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|x86 |x86-64
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #12 from voidcastr voidcastr@gmail.com 2012-12-11 02:46:15 CST --- (In reply to comment #11)
So, it's a bug in Mono???
I don't think so. The game ships its own version of mono, but since it's not crashing in windows, it's gotta be wine employing parts of that mono version in an erroneous way. This might be really hard to debug -- I'm currently not aware of a way of getting appropriate debug information out of a mono lib (i.e. the one shipped by the game) which was not compiled for that purpose.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #13 from jitsumi@gmail.com 2012-12-11 02:57:15 CST --- Yes, it's that i was thinking. So we should report a bug in wine about mono. I tried to find it a similar bug was already posted, but it's difficult to find such information...
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #14 from jitsumi@gmail.com 2012-12-11 03:03:25 CST --- Yes, it's that i was thinking. So we should report a bug in wine about mono. I tried to find it a similar bug was already posted, but it's difficult to find such information...
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #15 from jitsumi@gmail.com 2012-12-11 03:13:01 CST --- Hum... If we get a mono.dll with the debug symbols to replace the one that is provided with the game, we may have a more interested trace, no?
The problem is that i even don't know which version of mono they use...
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #16 from voidcastr voidcastr@gmail.com 2012-12-11 03:58:51 CST ---
If we get a mono.dll with the debug symbols to replace the one that is provided with the game, we may have a more interested trace, no?
Yep, that's what I thought as well. I think the game uses some mono 1.x version -- at least putting a mono 2.0 dll in place of the shipped mono.dll causes a crash complaining about some missing functions. However, in ".../Endless Space/EndlessSpace_Data/Mono/etc/mono/", there are "1.0" and "2.0" sub-folders... and since mono is open souce, it might even be possible that the Endless Space devs created an entirely custom mono.dll. In this case, we're pretty much screwed in terms of debugging. Anyway, I suppose we should check that and try with different 1.x version dlls.
So we should report a bug in wine about mono.
Definitely, but we need more information. The crash seems to occur in JITed C# code -> I'm not sure even debug symbols will help in this case. There is a wine dev (vpovrik) who seems to know much about these things... he's also the one who pointed me towards the MONO_DEBUG env var. I'm currently waiting for him to re-join IRC...
http://bugs.winehq.org/show_bug.cgi?id=32302
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #17 from jitsumi@gmail.com 2012-12-11 07:46:21 CST --- Ha, I found it: http://store.steampowered.com/news/8728/
I saw this version note, and remind that mac user needed to install mono. Apparently, it's the 2.11.3
But I'm also thinking that they make a special dll.....
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #18 from Vincent Povirk madewokherd@gmail.com 2012-12-11 10:29:22 CST --- It's a Unity game, so it's not a custom Mono. I don't think Unity puts anything special in their Mono build, but I could be wrong. Parts of Mono are LGPL so you may be able to contact the Endless Space devs and/or Unity devs to get the correct version and/or source code.
My hope with explicit-null-checks was that it would create a managed exception and thus get you a managed code backtrace from Mono itself. I wasn't expecting it to fix the problem. I guess this means the program is expecting a NULL reference and for some reason Mono isn't catching and translating the SEH exception properly. That would be the problem you need to solve, and a backtrace won't help with that.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #19 from jitsumi@gmail.com 2012-12-13 03:17:51 CST --- I asked of the tech suppor forum of the game if they know the version of mono.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #20 from jitsumi@gmail.com 2012-12-20 23:48:38 CST --- Apparently, Endless Space use unity 3.5.6. And apparently, from the release note of unity, unity use a mono v 2.6.3.
But they said that they fix some bug by themselves... so it is a modified version of mono 2.6.3
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #21 from jitsumi@gmail.com 2013-01-08 03:24:04 CST --- *** Bug 31336 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=32302
GyB gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69@gmail.com
--- Comment #22 from GyB gyebro69@gmail.com 2013-01-08 09:51:32 CST --- Hey jitsumi! Have you ever read my post in http://bugs.winehq.org/show_bug.cgi?id=31336#c10, and tried the game with native shlwapi (after winetricks ie6)? Native shlwapi works around the crash here when I load the saved game that you've provided in that forum post.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #23 from jitsumi@gmail.com 2013-01-08 10:32:13 CST --- Hello GyB !!!
I read about it, but I didn't have the time to try. I will try as soon as possible
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #24 from jitsumi@gmail.com 2013-01-09 01:01:10 CST --- This package does not work on a 64-bit installation
T_T
I'm reinstalling endless space in a win32 wine prefix...
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #25 from jitsumi@gmail.com 2013-01-09 02:00:49 CST --- Ok, winetricks ie6 works well. The game is not crashing anymore (for my save game, and for the the option "Auto Upgrade Ship Design in Queue")
But, in the same way that by using MONO_DEBUG=explicit-null-checks, I lose the music (not the sound, I still have the sound effect, but no music anymore)
http://bugs.winehq.org/show_bug.cgi?id=32302
jitsumi@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.5.19 |1.5.20
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #26 from jitsumi@gmail.com 2013-01-11 13:23:12 CST --- Btw, can someone confirm this bug to change its status to new?
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #27 from Vincent Povirk madewokherd@gmail.com 2013-01-11 13:42:41 CST --- It doesn't really matter; developers don't distinguish between unconfirmed and new.
http://bugs.winehq.org/show_bug.cgi?id=32302
GyB gyebro69@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|-unknown |shlwapi Ever Confirmed|0 |1
--- Comment #28 from GyB gyebro69@gmail.com 2013-01-11 13:46:06 CST --- I can confirm the crash and native shlwapi works around it. I just can't see how installing IE6 can cause music to stop for you. Music is still playing here after winetricks ie6.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #29 from jitsumi@gmail.com 2013-01-13 00:39:21 CST --- ^^' I still have the music sorry!
I went in the option after you told me that it doesn't happen to you, and in fact the sound level wasat the minimum for the music... (That's weird because I never changed that, I even never went in this option panel...)
Sorry!
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #30 from jitsumi@gmail.com 2013-01-17 03:35:19 CST --- One user in appdb confired that the problem come from shlwapi
He have the same king of crash, and he replace shlwapi for a native one, and now his game works well.
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #31 from jitsumi@gmail.com 2013-01-22 05:05:00 CST --- Well.. I tried to debug all that (with the debug channel) and, don't really see what 's going wrong...
For the debug channels for shlwapi, it is the channel shell and string I think.
I will try with winedebug, but first time i do this kind of stuff, if someone has some tips...
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #32 from jitsumi@gmail.com 2013-01-23 22:10:54 CST --- Just few questions if someone knows...
Do you know when the memeory dump happen? Is is when the crash occur, or after the crash?
And what means all the addresses? For example:
8 0x0058639a in endlessspace (+0x186399) (0x0032f3ec)
Is 0x0058639a the place of function in the memory and 0x0032f3ec in the file????
And what is +0x186399?
Thanks
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #33 from Vincent Povirk madewokherd@gmail.com 2013-02-18 15:32:58 CST --- Created attachment 43619 --> http://bugs.winehq.org/attachment.cgi?id=43619 patch disabling msvcrt's exception filter
It's a long shot, but does the attached patch make a difference?
http://bugs.winehq.org/show_bug.cgi?id=32302
--- Comment #34 from GyB gyebro69@gmail.com 2013-02-19 10:40:27 CST --- (In reply to comment #33)
Created attachment 43619 [details] patch disabling msvcrt's exception filter
It's a long shot, but does the attached patch make a difference?
Yes, the patch makes the crash go away (and it fixes the crash in bug #32541 as well).
http://bugs.winehq.org/show_bug.cgi?id=32302
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |juan.lang@gmail.com Component|shlwapi |msvcrt
--- Comment #35 from Vincent Povirk madewokherd@gmail.com 2013-02-19 10:59:47 CST --- Thanks, that establishes the component as msvcrt. Also CC'ing Juan Lang because he added the exception filter.
And before anyone asks, this is nothing to do with wine-mono. The affected application uses Mono successfully on Windows.
http://bugs.winehq.org/show_bug.cgi?id=32302
Piotr Caban piotr.caban@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |62e00e527fa67e3ddb043a61f68 | |13f471b380116 Status|NEW |RESOLVED CC| |piotr.caban@gmail.com Resolution| |FIXED
--- Comment #36 from Piotr Caban piotr.caban@gmail.com 2013-03-05 16:02:12 CST --- Fixed by commit: 62e00e527fa67e3ddb043a61f6813f471b380116.
http://bugs.winehq.org/show_bug.cgi?id=32302
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #37 from Alexandre Julliard julliard@winehq.org 2013-03-15 14:46:51 CDT --- Closing bugs fixed in 1.5.26.
-
wine-bugs＠winehq.org