https://bugs.winehq.org/show_bug.cgi?id=37618
Bug ID: 37618 Summary: wbemprox:enum_class_object_Next timeout not supported Product: Wine Version: 1.7.31 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wmi&wbemprox Assignee: wine-bugs@winehq.org Reporter: blue-t@web.de Distribution: ---
Since the recent updates to the Battle.Net and World Of Warcraft this line is repeatedly spammed in the logfile and it appears that the login and updates are taking longer
https://bugs.winehq.org/show_bug.cgi?id=37618
roger@mailinator.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |roger@mailinator.com
--- Comment #1 from roger@mailinator.com --- Are you sure it's because updates into game? And not because you (might have) updated wine?
https://bugs.winehq.org/show_bug.cgi?id=37618
--- Comment #2 from Ker noa blue-t@web.de --- yes
https://bugs.winehq.org/show_bug.cgi?id=37618
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download Status|UNCONFIRMED |NEW URL| |https://us.battle.net/accou | |nt/download/ CC| |focht@gmx.net Summary|wbemprox:enum_class_object_ |Battle.net agent spams |Next timeout not supported |console with | |'wbemprox:enum_class_object | |_Next timeout not | |supported' every 4 seconds Ever confirmed|0 |1 Severity|normal |minor
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello folks,
although there is some spam in console, the impact is not noticeable at all. Maybe if you have an ancient/crappy hardware (single core CPU).
I just checked myself.
--- snip --- $ WINEDEBUG=+tid,+timestamp ... ... 4585.801:0030:fixme:wbemprox:enum_class_object_Next timeout not supported 4589.842:0030:fixme:wbemprox:enum_class_object_Next timeout not supported 4593.895:0030:fixme:wbemprox:enum_class_object_Next timeout not supported 4597.932:0030:fixme:wbemprox:enum_class_object_Next timeout not supported 4601.967:0030:fixme:wbemprox:enum_class_object_Next timeout not supported ... --- snip ---
Another run to get more info (different pid/tids):
--- snip --- Wine-dbg>info process pid threads executable (all id:s are in hex) 00000094 42 'Battle.net.exe' 0000002e 23 'Agent.exe' 00000033 1 _ 'wineconsole.exe' 00000026 1 'explorer.exe' 0000000e 5 'services.exe' 00000019 3 _ 'plugplay.exe' 00000012 4 _ 'winedevice.exe' --- snip ---
--- snip --- Wine-dbg>info thread process tid prio (all id:s are in hex) ... 0000002e Agent.exe ... 00000043 0 ... 0000002f 0 00000033 wineconsole.exe 00000034 0 00000094 Battle.net.exe ... --- snip ---
Breakin to agent:
--- snip --- Wine-dbg>bt Backtrace: =>0 0x7d9f24a2 enum_class_object_Next(iface=0x140d10, lTimeout=0x3e8, uCount=0x1, apObjects=0x33fba8, puReturned=0x33fb94) [/home/focht/projects/wine/wine.repo/src/dlls/wbemprox/class.c:114] in wbemprox (0x0033fc18) 1 0x00464a7a in agent (+0x64a79) (0x0033fc60) 2 0x004631b5 in agent (+0x631b4) (0x0033fcd0) 3 0x0041f1ac in agent (+0x1f1ab) (0x0033fd18) 4 0x00401654 in agent (+0x1653) (0x0033fdac) 5 0x00406ada in agent (+0x6ad9) (0x0033fdd8) 6 0x0092b1a0 in agent (+0x52b19f) (0x0033fe20) ... --- snip ---
Trace log with WMI debug channel:
--- snip --- 0030:trace:wbemprox:wbem_services_ExecQuery 0x12bc78, L"WQL", L"SELECT ProcessId, ParentProcessId, ExecutablePath FROM Win32_Process", 0x00000020, (nil), 0x33fba0 0030:trace:wbemprox:grab_table returning 0x7da19300 0030:trace:wbemprox:parse_query wql_parse returned 0 0030:trace:wbemprox:fill_process created 7 rows 0030:trace:wbemprox:EnumWbemClassObject_create 0x33fba0 0030:trace:wbemprox:EnumWbemClassObject_create returning iface 0x131ff8 0030:trace:wbemprox:enum_class_object_Next 0x131ff8, 1000, 1, 0x33fba8, 0x33fb94 0030:fixme:wbemprox:enum_class_object_Next timeout not supported 0030:trace:wbemprox:create_class_object L"Win32_Process", 0x33fba8 0030:trace:wbemprox:create_class_object returning iface 0x133d70 0030:trace:wbemprox:class_object_Get 0x133d70, L"ProcessId", 00000000, 0x33fb74, (nil), (nil) 0030:trace:wbemprox:class_object_Get 0x133d70, L"ParentProcessId", 00000000, 0x33fb64, (nil), (nil) 0030:trace:wbemprox:class_object_Get 0x133d70, L"ExecutablePath", 00000000, 0x33fb84, (nil), (nil) 0030:trace:wbemprox:class_object_Release destroying 0x133d70 0030:trace:wbemprox:enum_class_object_Release destroying 0x131ff8 --- snip ---
The agent has a thread that periodically checks if the b.net launcher is still alive (4 secs). Since it's not the launcher or any game process that polls here using WMI, they can't be affected.
FIXME's are in many cases not bugs. You can always silence FIXME's on your own. Although timeout parameter support could be implemented it's *not* required for the apps/games to work.
A short-term "fix" would be a "once" FIXME if it bothers you.
$ wine --version wine-1.7.31-99-g5ecea72
Regards
https://bugs.winehq.org/show_bug.cgi?id=37618
Michael Müller michael@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |STAGED CC| |michael@fds-team.de, | |sebastian@fds-team.de Staged patchset| |https://github.com/wine-com | |pholio/wine-staging/tree/ma | |ster/patches/wbemdisp-Timeo | |ut
https://bugs.winehq.org/show_bug.cgi?id=37618
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |ea3dba9d6997fe1b3aee6e5fd35 | |cc6f6b6ab9bd2 Status|STAGED |RESOLVED Resolution|--- |FIXED
--- Comment #4 from Sebastian Lackner sebastian@fds-team.de --- The fixme's were silenced in http://source.winehq.org/git/wine.git/patch/ea3dba9d6997fe1b3aee6e5fd35cc6f6.... Marking fixed.
https://bugs.winehq.org/show_bug.cgi?id=37618
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.53.
-
wine-bugs＠winehq.org