[Bug 35814] New: SolidWorks 2013: sldProcMon hang up

http://bugs.winehq.org/show_bug.cgi?id=35814

Bug ID: 35814
           Summary: SolidWorks 2013: sldProcMon hang up
           Product: Wine
           Version: 1.7.14
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]

Created attachment 47813
  --> http://bugs.winehq.org/attachment.cgi?id=47813
WINEDEBUG=+relay,+tid,+seh on wine-1.7.14-126-g2bb1059

Steps to reproduce:
1) remove ~/.wine
2) winetricks vcrun2010 dotnet40
3) install SolidWorks 2013
4) wine sldProcMon.exe

Behaviour:
App hangs up using all CPU resources.

Expected behaviour:
App should start silently and close immediately.

Terminal output:
fixme:thread:GetThreadPreferredUILanguages 52, 0x33f978, 0x33fbf4 0x33f980
fixme:heap:HeapSetInformation (nil) 1 (nil) 0

[Bug 35814] SolidWorks 2013: sldProcMon hang up

http://bugs.winehq.org/show_bug.cgi?id=35814

--- Comment #1 from Nikolay Sivov  ---
Probably that's a problem:

---
0066:Call user32.FindWindowExW(00000000,00000000,0040f018
L"Shell_TrayWnd",0040e57c L"") ret=00407aca
0066:Ret  user32.FindWindowExW() retval=0001002e ret=00407aca
0066:Call user32.FindWindowExW(0001002e,00000000,0040f034
L"TrayNotifyWnd",0040e57c L"") ret=00407acd
0066:Ret  user32.FindWindowExW() retval=00000000 ret=00407acd
0066:Call user32.FindWindowExW(00000000,00000000,0040f050 L"SysPager",0040e57c
L"") ret=00407ad0
0066:Ret  user32.FindWindowExW() retval=00000000 ret=00407ad0
0066:Call user32.FindWindowExW(00000000,00000000,0040f064
L"ToolbarWindow32",00000000) ret=00407ad3
0066:Ret  user32.FindWindowExW() retval=00000000 ret=00407ad3
0066:Call user32.GetClientRect(00000000,0033fa48) ret=00407ae0
0066:Ret  user32.GetClientRect() retval=00000000 ret=00407ae0
0066:Call user32.SendMessageW(00000000,00000200,00000000,00000000) ret=00407b05
0066:Ret  user32.SendMessageW() retval=00000000 ret=00407b05
0066:Call user32.SendMessageW(00000000,00000200,00000000,00050000) ret=00407b05
0066:Ret  user32.SendMessageW() retval=00000000 ret=00407b05 
---

Shell_TrayWnd window is created by explorer, together with TrayNotifyWnd and
ToolbarWindow32 they're supposed to form a systray windows - these last two are
not created in Wine. No idea what SysPager is.

[Bug 35814] SolidWorks 2013: sldProcMon hang up

http://bugs.winehq.org/show_bug.cgi?id=35814

--- Comment #2 from NSLW  ---
Created attachment 47816
  --> http://bugs.winehq.org/attachment.cgi?id=47816
sldProcMon.png in system tray

(In reply to Nikolay Sivov from comment #1)
> Shell_TrayWnd window is created by explorer, together with TrayNotifyWnd and
> ToolbarWindow32 they're supposed to form a systray windows - these last two
> are not created in Wine. No idea what SysPager is.

Thanks for looking into the problem.

sldProcMon.exe doesn't close immediately if SolidWorks is running. Instead it
resides in tray (see attachment), so your clues about system tray are right.

sldProcMon.exe is described as "SolidWorks resource monitor" and it's purpose
is to display notifications in tray if resources are low (here is example when
it works https://forum.solidworks.com/message/396667).

I'm not expert but my first thoughts are that "SysPager" may be something
sldProcMon.exe is checking for resource usage or foremost whether SolidWorks is
running.

[Bug 35814] SolidWorks 2013: sldProcMon hang up

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

denis bonnenfant  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
                   |                            |g

--- Comment #3 from denis bonnenfant  ---
still there in SW 2014