The user32/win test crashes X on Intel cards

[Francois Gouget-2]

I hit this issue while trying to run winetest for WineConf. I looked
into it and the crash is caused by this line in dlls/user32/tests/win.c:

   SetWindowPos(hwnd, 0, 32768, 40000, 32768, 40000, SWP_NOMOVE);

More precisely it's the setting of the window width and height to
32768 x 40000 that causes the crash. Looking at the .xsession-errors
file I see the window manager reporting the following X server error:

Anomalie dans le gestionnaire de fenêtres : Unexpected X error: BadAlloc
(insufficient resources for operation) serial 11940 error_code 11
request_code 53 minor_code 0)

Is it possible that this is just an out of memory issue caused by the
huge window size? According to my tests 32000x32000 (a tad < 3GB) works
but 32767x32767 (a tad >3GB) cause the crash.

Here's my configuration:
 * Intel Corporation Mobile 945GME Express Integrated Graphics Controller rev 3
 * VideoRAM: 256MB (according to /var/log/Xorg.0.log)
 * xserver-xorg-video-intel 2:2.9.0-1
   Latest from Debian Testing.
   Debian Unstable does not seem to have a more recent driver.

Marcus got the same issue and he had an Intel card too and we were the
only two with this issue. So apparently this is Intel-specific.

Does any one have an Intel card where this does not happen? What's your
driver version?

--
Francois Gouget <fgouget@...>              http://fgouget.free.fr/
            "Lotto: A tax on people who are bad at math." -- unknown
          "Windows: Microsoft's tax on computer illiterates." -- WE7U

[Charles Davis-4]

Francois Gouget wrote:

> I hit this issue while trying to run winetest for WineConf. I looked
> into it and the crash is caused by this line in dlls/user32/tests/win.c:
>
>    SetWindowPos(hwnd, 0, 32768, 40000, 32768, 40000, SWP_NOMOVE);
>
> More precisely it's the setting of the window width and height to
> 32768 x 40000 that causes the crash. Looking at the .xsession-errors
> file I see the window manager reporting the following X server error:
>
> Anomalie dans le gestionnaire de fenêtres : Unexpected X error: BadAlloc
> (insufficient resources for operation) serial 11940 error_code 11
> request_code 53 minor_code 0)
>
> Is it possible that this is just an out of memory issue caused by the
> huge window size? According to my tests 32000x32000 (a tad < 3GB) works
> but 32767x32767 (a tad >3GB) cause the crash.
>
> Here's my configuration:
>  * Intel Corporation Mobile 945GME Express Integrated Graphics Controller rev 3
>  * VideoRAM: 256MB (according to /var/log/Xorg.0.log)
>  * xserver-xorg-video-intel 2:2.9.0-1
>    Latest from Debian Testing.
>    Debian Unstable does not seem to have a more recent driver.
>
> Marcus got the same issue and he had an Intel card too and we were the
> only two with this issue. So apparently this is Intel-specific.
>
> Does any one have an Intel card where this does not happen? What's your
> driver version?
>
>
>
> ------------------------------------------------------------------------
>
>

This happens on Mac OS X, too. Check out
http://xquartz.macosforge.org/trac/ticket/293

Chip

[Francois Gouget-2]

On Sun, 8 Nov 2009, Francois Gouget wrote:
[...]
> Here's my configuration:
>  * Intel Corporation Mobile 945GME Express Integrated Graphics Controller rev 3
>  * VideoRAM: 256MB (according to /var/log/Xorg.0.log)
>  * xserver-xorg-video-intel 2:2.9.0-1
>    Latest from Debian Testing.
>    Debian Unstable does not seem to have a more recent driver.


More data:
 * Marcus is running version 2.9.1 of the Intel driver (and gets the
   crash).
 * Michael Stefaniuc does not have the problem. He is using FC11's
   2.8.0 version of the driver.
 * I tried Michael's FC11 intel_drv.so file on my system and I still
   get a crash. I also tried the 2.8.1 Ubuntu driver and got the same
   result. So the problem comes from some other part of Xorg or the
   kernel.
 * Michael is running the 2.6.32 kernel and I'm running the 2.6.30 one.

--
Francois Gouget <fgouget@...>              http://fgouget.free.fr/
            "Lotto: A tax on people who are bad at math." -- unknown
          "Windows: Microsoft's tax on computer illiterates." -- WE7U

[Joerg-Cyril.Hoehle]

Hi,

>Marcus got the same issue and he had an Intel card too

Charles Davis wrote:
>This happens on Mac OS X, too. Check out
>http://xquartz.macosforge.org/trac/ticket/293

Charles forgot to mention that it affects NVidia on the Mac, which I did
not explicitly write in the above bug report (the Mac people will have
guessed it from the "early 2009 Mac mini" comment).

More precisely
        SetWindowPos(hwnd, 0, -32769, -40000, -32769, -90000, SWP_NOMOVE);
#if 0
        SetWindowPos(hwnd, 0, 32768, 40000, 32768, 40000, SWP_NOMOVE);
#endif
        SetWindowPos(hwnd, 0, -32769, -40000, -32769, -90000, SWP_NOSIZE);
        SetWindowPos(hwnd, 0, 32768, 40000, 32768, 40000, SWP_NOSIZE);
is enough to let the tests succeed with
Version:         2.3.3.2 (2.3.3)
Build Info:      X11server-480700~6
OS Version:      Mac OS X 10.5.7 (9J61)

This hints that the bug is in the X server, not the individual drivers?

Regards,
        Jörg Höhle

[Reece Dunn-2]

2009/11/9  <Joerg-Cyril.Hoehle@...>:

> Hi,
>
>>Marcus got the same issue and he had an Intel card too
>
> Charles Davis wrote:
>>This happens on Mac OS X, too. Check out
>>http://xquartz.macosforge.org/trac/ticket/293
>
> Charles forgot to mention that it affects NVidia on the Mac, which I did
> not explicitly write in the above bug report (the Mac people will have
> guessed it from the "early 2009 Mac mini" comment).
>
> More precisely
>        SetWindowPos(hwnd, 0, -32769, -40000, -32769, -90000, SWP_NOMOVE);
> #if 0
>        SetWindowPos(hwnd, 0, 32768, 40000, 32768, 40000, SWP_NOMOVE);
> #endif
>        SetWindowPos(hwnd, 0, -32769, -40000, -32769, -90000, SWP_NOSIZE);
>        SetWindowPos(hwnd, 0, 32768, 40000, 32768, 40000, SWP_NOSIZE);
> is enough to let the tests succeed with
> Version:         2.3.3.2 (2.3.3)
> Build Info:      X11server-480700~6
> OS Version:      Mac OS X 10.5.7 (9J61)
>
> This hints that the bug is in the X server, not the individual drivers?

Shouldn't this be cross-posted to the Xorg mailing list so that the
Xorg and driver devs can help out?

Also, does anyone know if it is possible to see what calls to the X
server are being made by these SetWindowPos calls (so that the Xorg
devs have a better idea of what is going on).

- Reece