Re: Semaphore handle leaks in WindowMaker with latest Xorg distribution

[Jon TURNEY <jon dot turney at dronecode dot org dot uk>]

Dr. Volker Zell wrote:
> Hi
>
> After switching to the latest Xorg packages (still under cygwin-1.5),
> WindowMaker-0.90.0-2 stops working after more or less 36 hours continues
> uptime of my laptop. When this happens I see the following in a bash window
> from where I started my X environment via startx:
>
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt () failed: 887601c2
>     winShadowUpdateDDNL - IDirectDrawSurface4_Blt failure message maximum (10) reached.  No more failure messages will be printed.
>     winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1
>     winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1
>     winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1
>     winBltExposedRegionsShadowDDNL - IDirectDrawSurface4_Blt reported that the primary surface was lost, trying to restore, retry: 1
>     XIO:  fatal IO error 105 (No buffer space available) on X server "127.0.0.1:0.0"
>           after 264481 requests (264320 known processed) with 0 events remaining.
>           7 [main] wmaker 2548 sig_send: wait for sig_complete event failed, signal -34, rc -1, Win32 error 6
>         200 [main] wmaker 2548 sig_send: wait for sig_complete event failed, signal -34, rc -1, Win32 error 6
>           7 [main] wmaker 2548 sig_send: wait for sig_complete event failed, signal -34, rc -1, Win32 error 6
>         200 [main] wmaker 2548 sig_send: wait for sig_complete event failed, signal -34, rc -1, Win32 error 6
>
>
>
>     XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
>           after 113314 requests (113269 known processed) with 0 events remaining.
>     xinit:  connection to X server lost.
>
>
> When using Task Manager I see that one of the two wmaker processes
> (the one started with wmaker --for-real) leaks handles with a rate of 30/sec
> right after stating up.
>
> When using process explorer from sysinternals I have to switch on
> "Show unnamed handles and mappings" under "View" to identify these handles
> as Semaphore types.
>
> Recompiling the latest version of WindowMaker-0.92.0 against the latest Xorg
> distribution has the same effect.
>
> I also checked running original WindowMaker-0.90.0-2 against cygwin-1.7 with
> all the latest packages installed and also recompiled WindowMaker-0.92.0 under
> cygwin-1.7 with the same effects.
>
>
> Can anybody confirm (at least the handle leaks in Task Manager) ?

Yes, I can see the same handle leak in task manager with windowmaker.

> WindowManager-0.90.0-2 runs absolutely stable with no leaks under cygwin 1.5
> before upgrading to latest Xorg.

So I guess suspicion first falls that this leak is somewhere in one of the 
updated X DLLs...

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/