Prefetch clearing should be repurposed to delete 0 sized read only .pf files only

VERIFIED FIXED in mozilla16

Status

()

Core
Widget: Win32
VERIFIED FIXED
5 years ago
5 years ago

People

(Reporter: bbondy, Assigned: bbondy)

Tracking

Trunk
mozilla16
x86_64
Windows 7
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa!])

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Once Bug 770883 lands on Nightly (currently v16) and gets uplifted to Aurora (currently v15), we should land a new patch from this bug on Nightly (currently v16) that will delete the prefetch files only if they are readonly and 0 bytes.  This patch will not get manually uplifted to Aurora, but will land there naturally on the next migration. 

This will effectively undo anyone's prefetch that is currently disabled.  This bug will NOT be requested to go onto Aurora (v15)
(Assignee)

Comment 1

5 years ago
Created attachment 639110 [details] [diff] [review]
Patch v1.
Attachment #639110 - Flags: review?(taras.mozilla)
(Assignee)

Updated

5 years ago
Blocks: 770911
(Assignee)

Updated

5 years ago
tracking-firefox15: ? → ---
(Assignee)

Updated

5 years ago
Target Milestone: --- → mozilla16

Comment 2

5 years ago
Comment on attachment 639110 [details] [diff] [review]
Patch v1.

This looks ok
Attachment #639110 - Flags: review?(taras.mozilla) → review+
(Assignee)

Comment 3

5 years ago
I tested this on Oak and it's working as it should.  I'll push this out in a couple days.
(Assignee)

Comment 4

5 years ago
http://hg.mozilla.org/integration/mozilla-inbound/rev/d00ae2e9b92a

Updated

5 years ago
QA Contact: jsmith
Whiteboard: [qa+]
https://hg.mozilla.org/mozilla-central/rev/d00ae2e9b92a
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
On a 7/15 inbound build, this isn't working for me on my home laptop (Win 7 32-bit). Info:

- In C:\Windows\Prefetch, there is one FIREFOX.PF file that is 0 KB and read only
- I've been running my browser for more than 20 minutes
- Maintenance service log only shows no activity by the prefetch service (no prefetch-like statements in the logs)
- The pref "app.update.service.lastVersionPrefetchCleared" is set to 16.0a1

Any ideas? I'll test on another machine tomorrow to confirm.
(In reply to Jason Smith [:jsmith] from comment #6)
> On a 7/15 inbound build, this isn't working for me on my home laptop (Win 7
> 32-bit). Info:
> 
> - In C:\Windows\Prefetch, there is one FIREFOX.PF file that is 0 KB and read
> only
> - I've been running my browser for more than 20 minutes
> - Maintenance service log only shows no activity by the prefetch service (no
> prefetch-like statements in the logs)
> - The pref "app.update.service.lastVersionPrefetchCleared" is set to 16.0a1
> 
> Any ideas? I'll test on another machine tomorrow to confirm.

Oh wait, I figured out the issue I hit. Resetting the pref caused the prefetch service to activate, resulting in removing the one Firefox PF 0 KB read only file.
So that verifies then for Windows 7 on inbound for the basic sanity test (wipe pref and see if prefetch file is wiped that is read only). Others to test:

- Windows XP - Basic sanity test for wiping prefetch files that are 0 KB and read only
- Windows Vista - Basic sanity test for wiping prefetch files that are 0 KB and read only
- Windows 7 - Update from FF 16 Nightly (prefetch enabled) to FF 17 Nightly (prefetch removal enabled), ensure wiping occurs
- Windows 7 - Switch from FF 16 Nightly (prefetch enabled) to FF 16 Aurora (prefetch removal enabled), ensure wiping occurs
- Windows 7 - Install FF 17 Nightly with prefetch files that > 0 KB, not read only, ensure that they are not wiped when prefetch service turns on
(Assignee)

Comment 9

5 years ago
Cool, ya this won't auto trigger for people until the migration.
Random question since we're doing cleanup tasks in these bugs - what are we going to do about the registry key that's created? Specifically:

HKEYLOCALMACHINE\SOFTWARE\Mozilla\MaintenanceService\FFPrefetchDisabled
(Assignee)

Comment 11

5 years ago
My plan was nothing :) If you uninstall the service it will be removed.  But if you want you can post for that and I'll implement something to handle it.
Tests Passed:

- Windows 7 - Basic sanity test for wiping prefetch files that are 0 KB and read only (pass)
- Windows XP - Basic sanity test for wiping prefetch files that are 0 KB and read only (pass)
- Windows Vista - Basic sanity test for wiping prefetch files that are 0 KB and read only (pass)
- Windows XP - Install FF 16 Nightly with prefetch files that > 0 KB, not read only, ensure that they are not wiped when prefetch service turns on (pass)
- Windows Vista - Update from FF 16 Nightly (prefetch enabled) to FF 17 Nightly (prefetch removal enabled), ensure wiping occurs (pass)

Tests still need to be run (will be done when next FF 16 Aurora build is available):

- Windows 7 - Switch from FF 16 Nightly (prefetch enabled) to FF 16 Aurora (prefetch removal enabled), ensure wiping occurs
Last test passes. Marking as verified. Will file a followup for the cleaning up registry issue.
Status: RESOLVED → VERIFIED
Whiteboard: [qa+] → [qa!]
You need to log in before you can comment on or make changes to this bug.