[Bug 37859] New: BOINC 6.x/7.x take a long time to "start" when launched from boincmgr
https://bugs.winehq.org/show_bug.cgi?id=37859 Bug ID: 37859 Summary: BOINC 6.x/7.x take a long time to "start" when launched from boincmgr Product: Wine Version: 1.7.33 Hardware: x86-64 URL: http://boinc.berkeley.edu/dl/boinc_7.4.36_windows_inte lx86.exe OS: Linux Status: NEW Keywords: download, performance, source Severity: trivial Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: imwellcushtymelike(a)gmail.com Distribution: Ubuntu Created attachment 50421 --> https://bugs.winehq.org/attachment.cgi?id=50421 Wine 1.7.33 / BOINC 7 console output There are a number of ways to start BOINC on a system: 1. At system startup (daemon/service). 2. On its own (in a console). 3. By launching boincmgr.exe (BOINC Manager). As of BOINC 6.x, option 3 can take around 60 seconds to "start". In reality the BOINC client (boinc.exe) starts immediately, just as quickly as any other way, but boincmgr.exe struggles repeatedly to connect. However: A. If BOINC is already running, boincmgr.exe connects instantly. B. If a second boincmgr.exe is launched immediately after the first (giving the few seconds for boinc.exe to start) it can connect immediately. C. boincmgr.exe can connect to any other client without any issue. So it's *just* when boincmgr.exe first launches boinc.exe that seems to confuse things.
From stdoutgui.txt:
[01/06/15 16:24:00] TRACE [9]: init_asynch() boinc_socket: 212 [01/06/15 16:24:00] TRACE [9]: init_asynch() connect: -1 [01/06/15 16:24:03] TRACE [9]: init_poll(): sock = 212 [01/06/15 16:24:04] TRACE [9]: init_poll(): sock = 212 [01/06/15 16:24:04] TRACE [9]: init_poll(): sock = 212 [...] [01/06/15 16:25:01] TRACE [9]: init_poll(): sock = 212 [01/06/15 16:25:01] TRACE [9]: asynch init timed out [01/06/15 16:25:01] TRACE [9]: init_asynch() boinc_socket: 212 [01/06/15 16:25:01] TRACE [9]: init_asynch() connect: -1 [01/06/15 16:25:01] TRACE [9]: init_poll(): sock = 212 [01/06/15 16:25:01] TRACE [9]: init_poll(): connected So it times out after 60 seconds and tries again with success. In comparison, scenario A gives: [01/06/15 16:41:13] TRACE [42]: init_asynch() boinc_socket: 216 [01/06/15 16:41:13] TRACE [42]: init_asynch() connect: -1 [01/06/15 16:41:14] TRACE [42]: init_poll(): sock = 216 [01/06/15 16:41:14] TRACE [42]: init_poll(): connected Tried both 32- and 64-bit binaries in both 32- and 64-bit WINEPREFIXes, same result each time. BOINC 5.8.16 does not have this problem. $ sha1sum boinc*.exe b4cdb23c8f51f33799c9d784ba38a9f69338fb68 boinc_5.8.16_windows_intelx86.exe c8dba7a184076240cdeef5032a9825a90244bb3f boinc_6.6.38_windows_intelx86.exe a67223afefb7072c82b366cab9d21e21ad2a719d boinc_7.0.64_windows_intelx86.exe 93f7a6639eca9bd7c8558146c2b23f954dffe9ef boinc_7.0.64_windows_x86_64.exe c86c17637d59ea12e78ed3fb56bb92beae897132 boinc_7.2.33_windows_intelx86.exe d761a1a57cf7836e2a33a5cd68ddb3bdd5e57af6 boinc_7.2.33_windows_x86_64.exe 277f9cf8007fe5f6901f6c04a4d3aa985fd172a9 boinc_7.2.42_windows_intelx86.exe d1f4f5de1ccef0977009800a9ff70321859b45b2 boinc_7.2.42_windows_x86_64.exe 2919cc9b6163019fc014a7fa4190bee8ead4b544 boinc_7.4.36_windows_intelx86.exe c2334aa9696f11a3f50dac07d1648c6b77ef9ae2 boinc_7.4.36_windows_x86_64.exe -- 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=37859 --- Comment #1 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Created attachment 50422 --> https://bugs.winehq.org/attachment.cgi?id=50422 WINE 1.7.33 / BOINC 7.0.64 stdoutgui.txt -- 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=37859 --- Comment #2 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- I forgot: err:ntdll:RtlpWaitForCriticalSection section 0x7bcd2f00 "loader.c: loader_section" wait timed out in thread 0045, blocked by 0044, retrying (60 sec) Probably related. -- 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=37859 --- Comment #3 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- No change in wine-1.7.44-199-g714abcb except that the err:ntdll:RtlpWaitForCriticalSection messages are gone, so that must have been unrelated. -- 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=37859 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- Fixed in wine-1.8-rc1 -- 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=37859 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #5 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 1.8-rc2. -- 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