New issue
Advanced search Search tips

Issue 741980 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Windows %TEMP% directory is being removed if it is empty

Reported by trent.c...@bpsoftware.net, Jul 13 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
1. Close Chrome
2. Browse to the %TEMP% directory and ensure it is empty
3. Browse to the Chrome User Data folder and rename Certificate Revocation Lists (or copy in an older version of the file)
4. Open Chrome
5. Browse to chrome://components
6. Ensure the %TEMP% directory is still empty
7. Click "Check for update" underneath CRLSet (or wait for the CRLSet update to run)

What is the expected behavior?
The temporary directories/files used by Chrome should be deleted but the %TEMP% (parent) directory should not be.

What went wrong?
The %TEMP% directory is being deleted.

Did this work before? N/A 

Chrome version: 59.0.3071.115  Channel: stable
OS Version: 10.0
Flash Version: 

This issue can affect other applications in the system if they are not checking/recreating the %TEMP% directory. 
It can also occur more frequently in terminal server/remote desktop services environments as each session is given a new (and unique) %TEMP% directory at logon based on their session id (see https://technet.microsoft.com/en-us/library/cc755098(v=ws.11).aspx).
 
Attached screenshots of API Monitor and Process Monitor captures when the directory is removed.
api-monitor-capture.png
113 KB View Download
process-monitor-capture.png
50.3 KB View Download
Cc: pbomm...@chromium.org
Components: Internals
Labels: Needs-Triage-M59
Cc: sorin@chromium.org waff...@chromium.org
Components: -Internals Internals>Installer>Components
Owner: waff...@chromium.org
Sorin and I will look into this, thanks for the report.
Status: Assigned (was: Unconfirmed)

Comment 5 by sorin@chromium.org, Jul 18 2017

Owner: sorin@chromium.org
Status: Started (was: Assigned)

Comment 7 by sorin@chromium.org, Jul 20 2017

Status: Fixed (was: Started)
Hi Sorin,
I can no longer reproduce this issue in the latest stable release (60.0.3112.78).

Could you please confirm if this bug was fixed in 60.0.3112.78? If not perhaps it might have been fixed in another issue?

I can still reproduce this issue in the previous stable release (59.0.3071.115).

Thanks

Sign in to add a comment