Hi Bruno,

I think this issue already exists since a long time - for example after running the user32/winstation tests.

I personally have not noticed that the probability has increased, but like with all random issues, even a

small delay / speedup can make it more or less likely to trigger such a random issue. If you can

reproduce it reliable enough, it would be nice if you could try to do a bisect (by running the corresponding

app/tests several times). The "bad" commit could be completely unrelated though.

BTW: After Qian pointed out the problem with explorer.exe process leaks some weeks ago, I've started

preparing patches for winstation and desktop cleanup. They also fix some race-conditions, but in their

current form I would consider them too experimental to be merged. Also, there are still a few unfixed

problems left.

Regards,

Sebastian

2015-12-01 20:20 GMT+01:00 Bruno Jesus <00cpxxx@gmail.com>:

I believe that since code freeze started (or maybe 1.7.55) a random
behavior was introduced related to these 2 messages:

err:winediag:nulldrv_CreateWindow Application tried to create a
window, but no driver could be loaded.
err:winediag:nulldrv_CreateWindow The explorer process failed to start.

Sometimes together there is also:
err:ole:apartment_createwindowifneeded CreateWindow failed with error 0

I'm not seeing this alone. at November 23 there was a mention to it in
bug https://bugs.winehq.org/show_bug.cgi?id=39384 and also in December
1 there was a mention at bug
https://bugs.winehq.org/show_bug.cgi?id=39057

The issue seems to manifest more when the computer is heavily loaded (cpu/ram).

I believe a regression test to be very hard since the issue is random, sorry.

Is anyone else affected by this? I'm still affected with today's git.

Best wishes,
Bruno