http://bugs.winehq.org/show_bug.cgi?id=27291
Summary: EVE Online - Intermittent Freezes On Window Focus Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: 7WCbywQg3N2H@dyweni.com
Hi,
I am running the following: * CPU - AMD Phenom II X6 1090T (clocked at 3.0 Ghz) * Linux Kernel 2.6.37-gentoo-r4 * X.Org Server 1.9.5 * OpenBox 3.4.11.2 * Wine GIT Commit 7f426a51d120c5ea790ba330c31db0043fd3e59b * EVE Online 6.44.259851
Wine is compiled for only 32bit applications. 64bit support was not enabled at compile time.
I play two EVE Online accounts at the same time. I start the EVE Clients with these commands:
$ cd ~/EVE/Installation $ export WINEPREFIX=~/EVE/wine1 $ wine explorer /desktop=EVE1,1279x1023 eve.exe & $ export WINEPREFIX=~/EVE/wine2 $ wine explorer /desktop=EVE2,1279x1023 eve.exe &
Both EVE Clients will play fine until I switch focus from one client to the other client. As soon as I switch focus to a non-Wine window or popup a window manager menu, both EVE Clients will appear to play "catch up" and then resume normal operation. I have no problems at all switching focus from one client to a non-Wine window and then to the other client.
I thought that this might be related to the XINPUT2 support, but running Wine with the '--without-xinput2' option enabled at compile time does not resolve the issue.
Any help that can be offered is much appreciated.
Thanks, Dyweni
http://bugs.winehq.org/show_bug.cgi?id=27291
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.3.20 Severity|normal |trivial
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #1 from 7WCbywQg3N2H@dyweni.com 2011-05-25 23:51:06 CDT --- I can confirm that this problem existed as of 1.3.17 (GIT COMMIT 123e4ad41d81bf4edc56eeab9f3cece9b511f690)
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #2 from 7WCbywQg3N2H@dyweni.com 2011-05-26 00:03:11 CDT --- I can confirm that this problem existed as of 1.3.12 (GIT COMMIT f0296a815e32ef954975b6c2a43951d4fff8ff09)
However, in 1.3.12, the problem was much worse. Switching focus to *any* window would cause the EVE Client to freeze. Switching focus back to the EVE Client would allow it to "catch up" but then it would re-freeze. The only way I have found to get it to "catch up" and stay unfrozen is to toggle a window manager menu and then focus back on the EVE client.
Additionally, I have found that in 1.3.12, two EVE Clients cannot be run concurrently using different Wine prefixes.
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #3 from 7WCbywQg3N2H@dyweni.com 2011-05-26 22:29:57 CDT --- I discovered a new fact:
From version 1.3.17 and on, switching back to the EVE Client from *any* window
is difficult to trigger, but can be triggered.
I've found it in the latest GIT COMMIT: 1ec78b8105653a3689548a9df887f36695c8361e
This bug was marked as trivial. If so, is there any particular location I should be looking at?
Thanks!
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #4 from 7WCbywQg3N2H@dyweni.com 2011-05-30 19:47:42 CDT --- Hello All!
I can confirm that the latest version of 1.3.21 (GIT Commit e6ee2c163ea445bca1d73d8e64a0ee3258c7f67c)
still does not solve this problem.
Thanks, Dyweni
http://bugs.winehq.org/show_bug.cgi?id=27291
7WCbywQg3N2H@dyweni.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.20 |1.3.21
--- Comment #5 from 7WCbywQg3N2H@dyweni.com 2011-05-30 20:39:16 CDT --- I've found that this also affects World of Warcraft game play.
It is really noticeable when running two EVE Clients and one World Of Warcraft client concurrently.
I've updated the version to reflect latest testing on my end. The title should be updated to reflect the fact that this occurs for more than just the EVE Online game.
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #6 from 7WCbywQg3N2H@dyweni.com 2011-09-04 15:39:51 CDT --- This is still a problem in the latest GIT pull: 32c36b7505e59d29c25e193e598e9edf8496066b
Some system components have been upgraded since the original post... here are the new specs:
* CPU - (same) * Linux Kernel 2.6.39-gentoo-r3 * X.Org Server 1.10.4 * OpenBox - (same) * Wine GIT Commit - 32c36b7505e59d29c25e193e598e9edf8496066b * EVE Online 7.11.288329
Does anyone have any ideas / thoughts / clues?
Thanks!
http://bugs.winehq.org/show_bug.cgi?id=27291
7WCbywQg3N2H@dyweni.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.21 |1.3.27
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #7 from 7WCbywQg3N2H@dyweni.com 2011-09-04 16:03:30 CDT --- Some additional specs: * Nvidia (Binary) Drivers 275.09.07 * X Input Protocol 2.0.2
Thanks!
http://bugs.winehq.org/show_bug.cgi?id=27291
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|1.3.27 |1.3.20
--- Comment #8 from Dmitry Timoshkov dmitry@baikal.ru 2011-09-07 02:25:18 CDT --- Please leave the Version field alone.
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #9 from 7WCbywQg3N2H@dyweni.com 2011-09-09 18:03:07 CDT --- (In reply to comment #8)
Please leave the Version field alone.
It was changed to indicate that it affects even the latest versions of WINE (including GIT)...
http://bugs.winehq.org/show_bug.cgi?id=27291
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #10 from Dan Kegel dank@kegel.com 2011-09-09 18:40:06 CDT --- The Version field is supposed to indicate the original wine version where the problem was noticed. It is assumed that the bug is also present in later versions. So please don't change it.
http://bugs.winehq.org/show_bug.cgi?id=27291
evanh evanh@clear.net.nz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |evanh@clear.net.nz
--- Comment #11 from evanh evanh@clear.net.nz 2011-09-17 08:34:44 CDT --- Old bug, well documented as bug 15485
Close this as a duplicate please.
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #12 from Dan Kegel dank@kegel.com 2011-09-17 08:41:56 CDT --- ZW, does the workaround from http://bugs.winehq.org/show_bug.cgi?id=15485#c100 help you?
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #13 from 7WCbywQg3N2H@dyweni.com 2011-09-17 22:34:52 CDT --- (In reply to comment #12)
ZW, does the workaround from http://bugs.winehq.org/show_bug.cgi?id=15485#c100 help you?
No, sorry. That workaround does not work. I can trigger the problem by simply firing up a couple of accounts and point & click between them - never once using Alt+TAB.
I'll also say that once the problem is triggered, X must be reset to make it go away. Simply closing all programs (minus Openbox) is not sufficient in making it go away.
Once the problem is initially triggered and all programs closed, the time from launching EVE until seeing it again varies, but it always gets seen again. Somehow, that time reduces itself as I begin to launch more and more accounts.
This is my latest configuration: * CPU - AMD Phenom II X6 1090T (clocked at 3.6 Ghz) * Linux Kernel 2.6.39-gentoo-r3 * X.Org Server 1.10.4 * X Input Protocol 2.0.2 * Nvidia (Binary) Drivers 275.09.07 * OpenBox - 3.4.11.2 * Wine GIT Commit - 3b40c03a8f0e3dcbb236d59125b115b2501086f8 * EVE Online 7.11.292761
I play multiple accounts simultaneously (usually 6, sometimes 8) (not using any kind of multiboxing / key / mouse broadcasting software - just point/click/type/etc in account 1, move to next account, rinse & repeat).
I've noticed the problem goes away by resetting X (ctrl-alt-backspace) and ONLY running EVE/WINE. As soon as I launch Chrome (the web browser) and surf a bit, the problem comes right back. I've seen other applications trigger the problem, but can't think what they are ATM.
I've even tried running WINE using 'nice -n 20', but that doesn't help here.
I run EVE with this series of commands: * export WINEPREFIX=/home/eve/wine$account * cd /home/eve/Installation * winecmd="wine explorer /desktop=EVE$account,$evesize bin/ExeFile.exe" * nice -n 20 $winecmd
I have found a second workaround (but resource hog) for those times when resetting X is not possible (due to open work, etc): * Run EVE using the same commands as above, but within its own TurboVNC server session with the VirtualGL wrapper. This isolates WINE into its own X environment, but still lets me use my primary video card for all the OpenGL rendering stuff. It's a resource hog because now I have two cores being used for each account.
Thanks, Dyweni
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #14 from 7WCbywQg3N2H@dyweni.com 2011-09-17 22:55:54 CDT --- Just to help things along, I just ran a simple test... 1. I've confirmed that the problem has been triggered. 2. I shutdown all problems (except window manager and did not restart X). 3. I fired up Chrome to compose this comment. 4. I fired up two accounts. 5. I verified that both accounts are responding normally. 6. Using a second computer SSH'd into this computer, I took an strace sample of the first wine account. Here's the strace command I ran: strace -f -p 14714 -c & sleep 5; kill %1 Here's the strace output: System call usage summary for 32 bit mode: % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 55.88 3.795426 2564 1480 select 42.44 2.882666 460 6269 1416 read 1.66 0.112983 112983 1 restart_syscall 0.02 0.001132 0 175056 gettimeofday 0.00 0.000103 0 9542 rt_sigprocmask 0.00 0.000076 0 3621 write 0.00 0.000042 0 3675 sched_yield 0.00 0.000031 0 1117 writev 0.00 0.000006 0 33 dup 0.00 0.000000 0 33 close 0.00 0.000000 0 236 getpid 0.00 0.000000 0 28 poll 0.00 0.000000 0 511 clock_gettime 0.00 0.000000 0 3 1 recvmsg ------ ----------- ----------- --------- --------- ---------------- 100.00 6.792465 201605 1417 total 7. I pointed and clicked several times between the two accounts to get WINE/EVE to "freeze". 8. I ran a second trace using the same command on the first wine instance. Here's the strace output for that trace: System call usage summary for 32 bit mode: % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 56.14 6.779976 4587 1478 select 43.78 5.287284 4170 1268 read 0.08 0.009797 0 202804 sched_yield 0.00 0.000301 0 6375 gettimeofday 0.00 0.000126 0 2368 rt_sigprocmask 0.00 0.000124 0 508 write 0.00 0.000083 0 645 writev 0.00 0.000009 0 31 dup 0.00 0.000000 0 31 close 0.00 0.000000 0 28 poll 0.00 0.000000 0 3 1 recvmsg ------ ----------- ----------- --------- --------- ---------------- 100.00 12.077700 215539 1 total 9. I clicked back on the Chrome window to "unfreeze" both wine instances.
Notice that I did not press Alt+TAB once during the whole sequence.
It appears that when the wine instances are "frozen", there is a massive increase of sched_yield calls, a massive decrease of gettimeofday calls, and no restart_syscall calls present.
Thanks, Dyweni
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #15 from Dan Kegel dank@kegel.com 2011-09-17 23:01:43 CDT --- Can you get the problem to happen, then do winedbg > log.txt 2>&1 btall quit and attach log.txt? And/or use gdb instead of strace and get stack traces from the livelocked process(es).
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #16 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:09:35 CDT --- A little more info - I tested killing openbox to see if it was a contributing factor.
My test sequence is this: 1. From the 2nd computer SSH'd into this one, make note of the /usr/bin/X and openbox pid #s. Killed the openbox process. 2. This caused XDM to present the normal XDM login screen. 3. Login and verify Openbox is present. 4. Verify /usr/bin/X has the same pid # but openbox has a new pid #. 5. Fire up two instances of EVE and see wine "freeze" almost instantly (even before I get to the game login prompt). 6. Fire up Chrome (Chrome has focus) and see wine "unfreeze".
Thanks, Dyweni
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #17 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:20:19 CDT --- Created an attachment (id=36437) --> (http://bugs.winehq.org/attachment.cgi?id=36437) winedbg output while livelocked
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #18 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:20:36 CDT --- Created an attachment (id=36438) --> (http://bugs.winehq.org/attachment.cgi?id=36438) winedbg output while not livelocked
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #19 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:21:43 CDT --- The only difference I see between the two winedbg outputs is:
--- log.txt 2011-09-17 23:16:38.671010153 -0500 +++ log2.txt 2011-09-17 23:17:54.097504297 -0500 @@ -205,7 +205,7 @@ 14 0x7efaf80e call_thread_entry_point+0x33(entry=0x7ee50132, arg=0x7ffdf000) [/usr/src/debug/app-emulation/wine-9999/wine-9999/dlls/ntdll/signal_i386.c:2499] in ntdll (0x0033ffb8) 15 0x7ef872a1 start_process+0x23(kernel_start=0x7ee50132) [/usr/src/debug/app-emulation/wine-9999/wine-9999/dlls/ntdll/loader.c:2612] in ntdll (0x0033ffe8) 16 0xf75ba511 wine_call_on_stack+0x1c() in libwine.so.1 (0x00000000) -0xf771b425 __kernel_vsyscall+0x5 in [vdso].so: movl $0x2b,%ecx +0xf6127d54: movl 0x0(%edi,%edx,4),%eax
Backtracing for thread 0032 in process 001f (Z:\root\EVE\Installation\bin\ExeFile.exe): Backtrace: @@ -404,5 +404,5 @@
Backtracing for thread 0020 in process 001f (Z:\root\EVE\Installation\bin\ExeFile.exe): Backtrace: -=>0 0xf771b425 __kernel_vsyscall+0x5() in [vdso].so (0xf52d86d8) - 1 0xf74d5b5c __sched_yield+0xb() in libc.so.6 (0xf52d7000) +=>0 0xf6127d54 in libnvidia-glcore.so.275.09.07 (+0xccad54) (0x00000004) + 1 0x00000000 (0x00000000)
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #20 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:35:44 CDT --- Looks like all instances of WINE "freeze" up while I have EVE running... I just tried with 1 WOW account in once instance and 1 EVE account in a second instance. WOW locks / unlocks at the same time that EVE does. However, after I close the EVE account, then I cannot reproduce with just the WOW account by itself.
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #21 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:42:47 CDT --- (In reply to comment #20)
Looks like all instances of WINE "freeze" up while I have EVE running... I just tried with 1 WOW account in once instance and 1 EVE account in a second instance. WOW locks / unlocks at the same time that EVE does. However, after I close the EVE account, then I cannot reproduce with just the WOW account by itself.
Let me take some of that back... I just got WOW to "freeze" up by itself... I ran winedbg with it frozen and not... Will attach now.
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #22 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:43:08 CDT --- Created an attachment (id=36439) --> (http://bugs.winehq.org/attachment.cgi?id=36439) wow - winedbg output while livelocked
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #23 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:43:27 CDT --- Created an attachment (id=36440) --> (http://bugs.winehq.org/attachment.cgi?id=36440) winedbg output while not livelocked
http://bugs.winehq.org/show_bug.cgi?id=27291
7WCbywQg3N2H@dyweni.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #36440|winedbg output while not |wow - winedbg output while description|livelocked |not livelocked
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #24 from 7WCbywQg3N2H@dyweni.com 2011-09-17 23:46:10 CDT --- Just checked out, compiled, tested latest GIT (ae80430feaef97e8bb0641384480c96a6dd191dd) and confirmed the problem still exists...
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #25 from Dan Kegel dank@kegel.com 2011-09-18 05:03:50 CDT --- Which process were you stracing?
Also, it's vaguely possible that this is related to the graphics driver. You might try switching to a different driver version (or even try with an ati card) just to see.
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #26 from evanh evanh@clear.net.nz 2012-06-16 21:37:21 CDT --- I'm still thinking it's a dup of http://bugs.winehq.org/show_bug.cgi?id=15485
Maybe the standard virtual desktop workaround didn't work for Dyweni's particular setup. But, as he found, a more severe partitioning did work.
I'm actually wondering if someone has found the cause and fixed it. As of December I've been happily back to running Eve without the virtual desktop. Although, I guess, Eve itself may have stopped doing some silly shit instead ...
http://bugs.winehq.org/show_bug.cgi?id=27291
--- Comment #27 from evanh evanh@clear.net.nz 2012-09-29 18:40:19 CDT --- Abandoned?
http://bugs.winehq.org/show_bug.cgi?id=27291
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |ABANDONED
--- Comment #28 from Austin English austinenglish@gmail.com 2012-10-01 13:33:29 CDT --- Yeah.
http://bugs.winehq.org/show_bug.cgi?id=27291
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |nerv@dawncrow.de
--- Comment #29 from André H. nerv@dawncrow.de 2012-10-02 05:52:26 CDT --- closing ABANDONED
-
wine-bugs＠winehq.org