X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=vEZPOMsihKDx88N5WLK3fSLL3jfqE017gWYak0R6xXBICbXv+tk80
	TieJyPZKPyp1UFIGKQUoUiDefVdUyhl5MfGhRRfQ5WZgHA/Q99XI9NQy9VF96Vt5
	lncL58+5J+zV4WFL34mZnAIit7p9yGC1hqxqBNp9PWVUNYinV1QxXY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	 bh=LKxoEPeHxIVMVyw5MVyyFSscdDk=; b=UGirxVFTOUuqbWLRvVFUuD4ceuG6
	jjaLtAPIAGLoviwpAUOyAK2txgPrCe0G3ymWers+N6AAvNk/v2cVju/aDpxF2nzW
	eBtVXVahzx9dEIIakxqZTY45A1tULzRo9p01aq7bGnPKgFs+JaB442LkGOM2bGMC
	PZX4fbOxs1Vjuug=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-100.9 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=row, H*F:D*cygwin.com, H*MI:sk:2019030
X-HELO: mout.kundenserver.de
Date: Mon, 4 Mar 2019 17:06:30 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Cc: cygwin AT cygwin DOT com
Subject: Re: cygwin snapshots after 23, Feb. ocasionally destroys windows logon session
Message-ID: <20190304160630.GH3785@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>,	cygwin AT cygwin DOT com
References: <20190305002849 DOT fdb1c8db14f8f83e5210553f AT nifty DOT ne DOT jp> <20190304155705 DOT GG3785 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="KIzF6Cje4W/osXrF"
Content-Disposition: inline
In-Reply-To: <20190304155705.GG3785@calimero.vinschen.de>
User-Agent: Mutt/1.11.3 (2019-02-01)

--KIzF6Cje4W/osXrF
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar  4 16:57, Corinna Vinschen wrote:
> On Mar  5 00:28, Takashi Yano wrote:
> > Hi Corinna,
> >=20
> > I encountered a problem with cygwin snapshots after 23, Feb.
> > If I login to cygwin via ssh and logout from ssh session,
> > explorer sometimes gets into erroneous state. Most of
> > operations cannot be done on explorer.
> >=20
> > This does not happen in all environments, however,
> > at least two of my machines are affected.
> >=20
> > * Windows 7 64bit machine with 32bit cygwin installed.
> > * Windows 10 64bit machine with 32bit cygwin installed.

FTR, I just reproduced it after the fifth logon/logoff in a row
on W10 64 bit w/ 64 bit Cygwin.


Corinna


> >=20
> > To reproduce this, logon windows with a user and start
> > cygwin. Then, repeat login and logout via cygwin ssh/sshd
> > a few ten times with the user who logon to windows.
> >=20
> > I looked into this problem, and found the culprit.
> >=20
> > The following modification seems to cause this problem.
>=20
> You sure?  If you revert that single patch, all is well even after
> multiple ssh logon/logoff attempts?
>=20
> > But I am not sure what is wrong with this code.
>=20
> No, I don't get it either.
>=20
> > Is this code really necessary?
>=20
> It's probably not necessary, at least we hadn't had anything like that
> before.  As you can see from commits 71b8777a7140, 8eee25241e86,
> dd3730ed9c1c and bcb33dc4f055, the idea is to unload a user profile if
> it's not used anymore.
>=20
> I'm puzzled that calling UnloadUserProfile should actually unload a user
> profile if it's still in use by the interactive session.  That sounds
> like a bug in Windows to me, but what do I know?
>=20
> I can revert this single patch, or I can revert the above patchset
> trying to unload a user profile entirely, whatever makes more sense.
>=20
> However, what makes most sense?!?

--KIzF6Cje4W/osXrF
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlx9TQUACgkQ9TYGna5E
T6AZRA//Xlhg/FLm9pgWDbJbt+c83geJ0xHVovColiKGtlHTuDlU9lqIRPSBrQ5X
I2qpsbBQnOXUaeD0zntc7EE6Gvqr6gt4zDi548jI8PGQzeTpK3GvQbNwmFph2tYW
kGKmk5JsITZo5yF5Phe9kfQhULrmdhn6yHfTGm7/7GV/iQYoJI1sCJiA/qq43kkX
rdnlvitUlMaKsd0vRfLDNkwkc440I00qBDR1Ad3C8HFNM8qkvbug5OMF35Py47kY
FJtZaRtcCwL91xbTTFm13yzy91raaehJo+nuPh/doS662DQ8M20wat9Im3msDZ1U
Qs6dlZzU9ithccNs00MrT0yI1AD8jTLe2DWNkL84xj4WksgQGEl/t/LWymAgZDBt
1gmdeBNUqUsy4ENhI2nnalYm0NlIbbNlZ+znhzFuuh2OPRZNS2aZaUg3ueTOeV5D
mSkl0rqJg7c/i4/yVIyhbgCA6dAHW3xRTzkEJFpnlp0rLxIfyoXw/zMuEjvmme7n
2ZIfSHO9CLFVukvm21rBhjODMYdeRiLq44LHIlxyABzsYJoesTVLY0QeTF9ifoMc
nqQfUwec0xRsyltjqawXBiP7U+zULXopFwJQpQmzJfbkuOmG5JCyKMTT9j8Y41TV
/us1VriGFnXMAhIXxaXiQulzw9z0NM/oGNGYPwY+eMFdduOg8/M=
=0vaG
-----END PGP SIGNATURE-----

--KIzF6Cje4W/osXrF--