These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Linux

 
  • Topic is locked indefinitely.
 

New launcher on singularity

First post
Author
Previous Topic Next Topic
Kadesh Priestess
Descendance.
GoonSwarm.
#1 - 2015-02-26 19:49:53 UTC
The one which lets you to play the game as it's being downloaded.

It crashes under wine 1.7.29 for me (with vcrun2008 installed/not installed), anyone experiences similar issues? It stops crashing if you map web.ccpgamescdn.com to localhost, but then it obviously doesn't work at all.
Torgeir Hekard
I MYSELF AND ME
#2 - 2015-02-27 03:29:36 UTC
Set windows version to WinXP. Then it works. Kinda. Crashes on trying to access settings.
Kismeteer
Bat Country
Pandemic Horde
#3 - 2015-02-27 21:12:59 UTC
I have the same crash on settings as well, but everything else seems like it works pretty well.

fixme:win:EnumDisplayDevicesW ((null),0,0x33c688,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33c408,0x00000000), stub!
fixme:d3d11:D3D11CreateDevice stub: adapter 0x6b7bf08, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0, feature_levels 3393716, levels 0x1, sdk_version 7, device 0x33c8cc, feature_level 0x33c8b0, context 0x33c8c0
fixme:win:EnumDisplayDevicesW ((null),0,0x33c688,0x00000000), stub!
fixme:win:EnumDisplayDevicesW ((null),0,0x33c408,0x00000000), stub!
fixme:d3d11:D3D11CreateDevice stub: adapter 0x67c4ae0, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0, feature_levels 3393716, levels 0x1, sdk_version 7, device 0x33c8cc, feature_level 0x33c8b0, context 0x33c8c0
fixme:win:EnumDisplayDevicesW ((null),0,0x33c5a8,0x00000000), stub!
fixme:d3d11:D3D11CreateDevice stub: adapter 0x6b618f0, driver_type D3D_DRIVER_TYPE_UNKNOWN, swrast (nil), flags 0, feature_levels 3394132, levels 0x1, sdk_version 7, device 0x33ca6c, feature_level 0x33ca50, context 0x33ca60
fixme:shell:SHGetStockIconInfo (79, 0x100, 0x33ca00) semi-stub
fixme:shell:SHGetStockIconInfo flags 0x100 not implemented
wine: Unhandled page fault on read access to 0x00000000 at address 0x1df88e3 (thread 002b), starting debugger...


Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x01df88e3).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:01df88e3 ESP:0033c450 EBP:06a55560 EFLAGS:00210286(  R- --  I S - -P- )
 EAX:00000000 EBX:00000007 ECX:00000000 EDX:0033c4b0
 ESI:06bbf8e8 EDI:0033c4f8
Stack dump:
0x0033c450:  88737c14 0033c4f8 06bbf8e8 06a55560
0x0033c460:  00000007 01d772fe 88737c2c 0033c51c
0x0033c470:  01e6dcfb ffffffff 01dfb518 0033c4f8
0x0033c480:  06bbf8e8 06bbf8e8 02914519 0033c4b0
0x0033c490:  88731632 06bb4ab0 06bbf8e8 02cdc7a0
0x0033c4a0:  06bb4ab0 00000007 0028040a 06a55560
000c: sel=0067 base=00000000 limit=00000000 32-bit r-x


System information:
    Wine build: wine-1.6.2
    Platform: i386 (WOW64)
    Host system: Linux
    Host version: 3.13.0-45-generic
Kadesh Priestess
Descendance.
GoonSwarm.
#4 - 2015-03-02 18:58:28 UTC
On winXP setting it indeed does.
Torgeir Hekard
I MYSELF AND ME
#5 - 2015-03-03 11:18:28 UTC  |  Edited by: Torgeir Hekard
By the way, I ran the launcher with WINEDEBUG=+relay, and in both cases (crash on startup when setting windows version to Win7 and crash on cogwheel when using windows XP) the trace is pretty similar around the crash (down to instruction pointer), so both crashes probably have the same cause.

This is for the cogwheel:


0034:Call msvcr90.wcslen(03553378 L"Browse") ret=7db280fd
0034:Ret  msvcr90.wcslen() retval=00000006 ret=7db280fd
0034:Call msvcr90.memcpy_s(0033c474,0000000e,03553378,0000000c) ret=7db28147
0034:Ret  msvcr90.memcpy_s() retval=00000000 ret=7db28147
0034:Ret  msvcp90.??0?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QAE@PB_W@Z() retval=0033c470 ret=019672b6
0034:Call msvcr90.free(03553378) ret=019672ed
0034:Call ntdll.RtlFreeHeap(00480000,00000000,03553378) ret=7e8d9d3e
0034:Ret  ntdll.RtlFreeHeap() retval=00000001 ret=7e8d9d3e
0034:Ret  msvcr90.free() retval=00000001 ret=019672ed
0034:Call msvcr90.??3@YAXPAX@Z(03553390) ret=019672f6
0034:Call ntdll.RtlFreeHeap(00480000,00000000,03553390) ret=7e8d9d3e
0034:Ret  ntdll.RtlFreeHeap() retval=00000001 ret=7e8d9d3e
0034:Ret  msvcr90.??3@YAXPAX@Z() retval=00000001 ret=019672f6
0034:Call msvcp90.??0?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QAE@XZ(0033c4b8) ret=0195b779
0034:Ret  msvcp90.??0?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QAE@XZ() retval=0033c4b8 ret=0195b779
0034:Call msvcp90.?c_str@?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QBEPB_WXZ(0033c470) ret=019b95f2
0034:Ret  msvcp90.?c_str@?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QBEPB_WXZ() retval=0033c474 ret=019b95f2
0034:Call msvcr90._except_handler4_common(00405a90,00403086,0033c3cc,0033fe50,0033c100,0033c03c) ret=00402fa5
0034:Call msvcr90._XcptFilter(c0000005,0033bf18) ret=00402b2c
0034:Ret  msvcr90._XcptFilter() retval=00000000 ret=00402b2c
0034:Ret  msvcr90._except_handler4_common() retval=00000001 ret=00402fa5
0034:Call KERNEL32.UnhandledExceptionFilter(0033bf78) ret=7bc99845
wine: Unhandled page fault on read access to 0x4f75d2b5 at address 0x19b9602 (thread 0034), starting debugger...


And this is for the Win7


0036:Call msvcr90.wcslen(0328cbd0 L"Yes") ret=7db2c0fd
0036:Ret  msvcr90.wcslen() retval=00000003 ret=7db2c0fd
0036:Call msvcr90.memcpy_s(0033ece0,0000000e,0328cbd0,00000006) ret=7db2c147
0036:Ret  msvcr90.memcpy_s() retval=00000000 ret=7db2c147
0036:Ret  msvcp90.??0?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QAE@PB_W@Z() retval=0033ecdc ret=019672b6
0036:Call msvcr90.free(0328cbd0) ret=019672ed
0036:Call ntdll.RtlFreeHeap(00480000,00000000,0328cbd0) ret=7e8cdd3e
0036:Ret  ntdll.RtlFreeHeap() retval=00000001 ret=7e8cdd3e
0036:Ret  msvcr90.free() retval=00000001 ret=019672ed
0036:Call msvcr90.??3@YAXPAX@Z(03289e10) ret=019672f6
0036:Call ntdll.RtlFreeHeap(00480000,00000000,03289e10) ret=7e8cdd3e
0036:Ret  ntdll.RtlFreeHeap() retval=00000001 ret=7e8cdd3e
0036:Ret  msvcr90.??3@YAXPAX@Z() retval=00000001 ret=019672f6
0036:Call msvcp90.??0?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QAE@XZ(0033ed00) ret=0195b779
0036:Ret  msvcp90.??0?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QAE@XZ() retval=0033ed00 ret=0195b779
0036:Call msvcp90.?c_str@?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QBEPB_WXZ(0033ecdc) ret=019b95f2
0036:Ret  msvcp90.?c_str@?$basic_string@_WU?$char_traits@_W@std@@V?$allocator@_W@2@@std@@QBEPB_WXZ() retval=0033ece0 ret=019b95f2
0036:Call msvcr90._except_handler4_common(00405a90,00403086,0033ec4c,0033fe50,0033e980,0033e8bc) ret=00402fa5
0036:Call msvcr90._XcptFilter(c0000005,0033e798) ret=00402b2c
0036:Ret  msvcr90._XcptFilter() retval=00000000 ret=00402b2c
0036:Ret  msvcr90._except_handler4_common() retval=00000001 ret=00402fa5
0036:Call KERNEL32.UnhandledExceptionFilter(0033e7f8) ret=7bc99845
wine: Unhandled page fault on read access to 0x3932e469 at address 0x19b9602 (thread 0036), starting debugger...


Probably should try running the launcher on an actual later windows version and see how it looks there. Especially the Pre-Release warning popup.
Frunje Elbris
Bovine Ltd.
#6 - 2015-03-04 11:43:39 UTC
Apart from cogwheel problem, launcher on my setup [when I run it for the first time after server update] freezes for minute or two on phase "downloading cache update 0/250MB" or something like that, without any visible progress. It just finally switch to "Client is ready" state.

I get that freeze is just display bug, and it downloads the stuff on background, but it feels like too much data, when the point of DoD launcher is to make launching faster. [And client does DoD, so it is not updating whole cache every day by launcher]
Torgeir Hekard
I MYSELF AND ME
#7 - 2015-03-04 12:25:22 UTC
Frunje Elbris wrote:
Apart from cogwheel problem, launcher on my setup [when I run it for the first time after server update] freezes for minute or two on phase "downloading cache update 0/250MB" or something like that, without any visible progress. It just finally switch to "Client is ready" state.

I get that freeze is just display bug, and it downloads the stuff on background, but it feels like too much data, when the point of DoD launcher is to make launching faster. [And client does DoD, so it is not updating whole cache every day by launcher]

Some dev commented somewhere that the launcher counts progress in the number of files, not their volume. And the initial download is one really big file taking more than half of the download volume and some smaller files. So during the initial download you get a frozen progress bar while the big file is being downloaded.
Torgeir Hekard
I MYSELF AND ME
#8 - 2015-03-04 18:49:28 UTC
New launcher build. The crash is fixed. Both crashes, in fact.
CCP Atropos
C C P
C C P Alliance
#9 - 2015-03-08 18:46:23 UTC
It was due to the version of wxPython in use. It was using 3.0.0.0 on Windows which would crash on Win XP (and thus Wine when running as Win XP). Updating to 3.0.2.0 fixed the problem.
Torgeir Hekard
I MYSELF AND ME
#10 - 2015-03-20 16:44:39 UTC
The new laucher now periodically hangs for me on startup.
That is, it's worse each time. Several days ago it was only doing it from time to time, but now a successful start is a miracle.

WINEDEBUG=+relay is indefinitely looping with

0039:Call ntdll.RtlTryEnterCriticalSection(05330d0c) ret=0416a10a
0039:Ret  ntdll.RtlTryEnterCriticalSection() retval=00000001 ret=0416a10a
0039:Call KERNEL32.Sleep(00000001) ret=0416af61