[Bug 52383] New: Wxwork: high CPU usage (on login)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

Bug ID: 52383
           Summary: Wxwork: high CPU usage (on login)
           Product: Wine-staging
           Version: 7.0-rc5
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
                CC: [e-mail], [e-mail]
      Distribution: ---

Created attachment 71598
  --> https://bugs.winehq.org/attachment.cgi?id=71598
winsock trace

1、download wxwork(message tools,like wechat)
 https://work.weixin.qq.com/wework_admin/commdownload?platform=win&from=b...
2、install to c:\Program Files\wxwork
  sha1sum WeCom_4.0.0.6003.exe
  f6793cadd16ee5908c20ce310fb8e35243356f9e  WeCom_4.0.0.6003.exe

du -shc WeCom_4.0.0.6003.exe 
   387M    WeCom_4.0.0.6003.exe
   387M    总用量
3、/home/ihxy/.wine/drive_c/Program Files/WXWork
  run WINEDEBUG=-all,+winsock wine WXWork.exe
4、you will see:
b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3fc3f0,
in_size 28, out_buffer 0xb3fc3f0, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3fc3f0,
in_size 28, out_buffer 0xb3fc3f0, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb478d18,
in_size 28, out_buffer 0xb478d18, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb478d18,
in_size 28, out_buffer 0xb478d18, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb478d18,
in_size 28, out_buffer 0xb478d18, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cb020,
in_size 28, out_buffer 0xb3cb020, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cb020,
in_size 28, out_buffer 0xb3cb020, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cb020,
in_size 28, out_buffer 0xb3cb020, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cb020,
in_size 28, out_buffer 0xb3cb020, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cb020,
in_size 28, out_buffer 0xb3cb020, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cb020,
in_size 28, out_buffer 0xb3cb020, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cb020,
in_size 28, out_buffer 0xb3cb020, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28
0b2c:trace:winsock:select read 0B485F90, write 0B486FA0, except 0B487FB0,
timeout 1D6BFA4C
0b2c:trace:winsock:sock_ioctl handle 0x4bc, code 0x12024, in_buffer 0xb3cd298,
in_size 28, out_buffer 0xb3cd298, out_size 28

[Bug 52383] Wxwork: high CPU usage (on login)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

--- Comment #1 from ihxy  ---
it seems duplicate with
https://bugs.winehq.org/show_bug.cgi?id=10497
the bug still occur with current wine(wine-staging 7.0-rc5)

[Bug 52383] Wxwork: high CPU usage (on login)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

--- Comment #2 from ihxy  ---
(In reply to ihxy from comment #1)
> it seems duplicate with
> https://bugs.winehq.org/show_bug.cgi?id=10497
> the bug still occur with current wine(wine-staging 7.0-rc5)

sorry, i reference a error bug url,the correct reference bug is 
https://bugs.winehq.org/show_bug.cgi?id=51442

[Bug 52383] Wxwork: high CPU usage (on login)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

--- Comment #3 from Jactry Zeng  ---
(In reply to ihxy from comment #2)
> (In reply to ihxy from comment #1)
> > it seems duplicate with
> > https://bugs.winehq.org/show_bug.cgi?id=10497
> > the bug still occur with current wine(wine-staging 7.0-rc5)
>
> sorry, i reference a error bug url,the correct reference bug is 
> https://bugs.winehq.org/show_bug.cgi?id=51442

Wine 7.0-rc5 already included the fix for bug 51442.
Do you mean that the issue you saw on WXWork is also a regression caused by
commit 414b31bc0bbbfe005e90a1946a649082dc303c55?

[Bug 52383] Wxwork: high CPU usage (on login)

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

--- Comment #4 from ihxy  ---
i couldn't install wine-devel-6.11 for now:

sudo apt install winehq-devel=6.11~focal-1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 winehq-devel : Depends: wine-devel (= 6.11~focal-1)
E: Unable to correct problems, you have held broken packages.

I'will find another way to install it, just wait a few days.

[Bug 52383] WXWork has high CPU usage on login screen

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

Zebediah Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Wxwork: high CPU usage (on  |WXWork has high CPU usage
                   |login)                      |on login screen
    Regression SHA1|                            |414b31bc0bbbfe005e90a1946a6
                   |                            |49082dc303c55
          Component|-unknown                    |winsock
           Keywords|                            |download, regression
                URL|                            |https://work.weixin.qq.com/
                   |                            |wework_admin/commdownload?p
                   |                            |latform=win&from=baidu
                 CC|[e-mail] |
            Product|Wine-staging                |Wine

--- Comment #5 from Zebediah Figura  ---
I can reproduce the bug; I've sent
https://source.winehq.org/patches/data/223439. That means it is almost
certainly a regression from 414b31bc0.

[Bug 52383] WXWork has high CPU usage on login screen

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

Zebediah Figura  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
      Fixed by SHA1|                            |894679ced80ec4bbedff37babae
                   |                            |3f89592bd7ae7
         Resolution|---                         |FIXED

--- Comment #6 from Zebediah Figura  ---
Fixed by
https://source.winehq.org/git/wine.git/commitdiff/894679ced80ec4bbedff37babae3f89592bd7ae7.

[Bug 52383] WXWork has high CPU usage on login screen

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

--- Comment #7 from ihxy  ---
I confirm that fixed in wine-7.0-rc6
thx, Zebediah Figura

[Bug 52383] WXWork has high CPU usage on login screen

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=52383

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #8 from Alexandre Julliard  ---
Closing bugs fixed in 7.1.