On Wed, Dec 2, 2015 at 9:54 PM, Sebastian Lackner sebastian@fds-team.de wrote:
Hi Bruno,
Lali-ho!
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.
Thanks for the reply. I don't remember ever seeing those messages, I'm trying to make it easier to reproduce here. What I have always randomly experienced is other error (which also have a bug I can't remember) and it is something like wine_kernel_boot: timeout, or wine_kernel_init or something like that.
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.
I'll wait for your patches them, after restarting the computer the error seems to be happening less so I believe it is related to the amount of memory used.
Bruno