Re: [PATCH] explorer: make process as system process.
Qian Hong <qhong(a)codeweavers.com> writes:
One possible solution is to count threads as users rather than processes, but explorer.exe itself could have more than on thread, which makes this way complex. The attached patch use another way, just make explorer.exe an system process, and it will quit automatically few seconds after all user process exit. I don't know if there is a historical reason not to make explorer.exe a system process, or if there is a compatible reason, any background is great appreciated.
It's possible to create multiple virtual desktops, and you want them to go away once they are no longer used. You can't have a bunch of desktop windows stay around until the last app exits. -- Alexandre Julliard julliard(a)winehq.org
On Fri, Nov 20, 2015 at 11:30 AM, Alexandre Julliard <julliard(a)winehq.org> wrote:
It's possible to create multiple virtual desktops, and you want them to go away once they are no longer used. You can't have a bunch of desktop windows stay around until the last app exits.
Thanks for the information! I'll think a bit more about the refcount way. -- Regards, Qian Hong - http://www.codeweavers.com
On 20.11.2015 06:25, Qian Hong wrote:
On Fri, Nov 20, 2015 at 11:30 AM, Alexandre Julliard <julliard(a)winehq.org> wrote:
It's possible to create multiple virtual desktops, and you want them to go away once they are no longer used. You can't have a bunch of desktop windows stay around until the last app exits.
Thanks for the information! I'll think a bit more about the refcount way.
When looking at the logs, the problem is pretty clear. The problem is that when the explorer.exe process is the only user, a shutdown timeout is never started. Something like http://ix.io/mmu would fix the problem, but it needs more thoughts - for example, if additional protections against race-conditions are required. Regards, Sebastian
participants (3)
-
Alexandre Julliard -
Qian Hong -
Sebastian Lackner