Closed Bug 685136 Opened 13 years ago Closed 10 years ago

Firefox doesn't delete local shared objects (LSO) on exit or using "clear recent history"

Categories

(Firefox :: General, defect)

6 Branch
x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 607908

People

(Reporter: drey12, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 Build ID: 20110902133214 Steps to reproduce: Cleared all cookies using "clear recent history" or configured Firefox to clear my cookies automatically upon exit Actual results: Flash Player settings manager in Windows 7 Control Panel still contained LSOs for sites i visited. Expected results: Flash Player settings manager in Windows 7 Control Panel should not contain LSOs for sites i visited, they should be deleted. Flash 10.3.183.7
Did you include the cookies with "clear recent history" ?
(In reply to Matthias Versen (Matti) from comment #1) > Did you include the cookies with "clear recent history" ? Yes.
Did you have the time range in "Clear recent history" set to "Everything"?
(In reply to mjh563 from comment #3) > Did you have the time range in "Clear recent history" set to "Everything"? Yeah, I tried that. Tested more. Seems like Firefox only deletes them if you are browsing a tab open with website which issues LSOs. Even tried Private Browsing - it works properly. The issue is in usual mode. Also Firefox never clears those super-cookies automatically upon exit even if set to do so.
Same in FF 7.0 Beta. I have FF set to delete all cookies upon closing the browser, but Flash cookies are still present after restarting Firefox. FF version is Mozilla/5.0 (Windows NT 6.1; rv:7.0) Gecko/20100101 Firefox/7.0 Flash version is 10.3 r183
My bad - works for me now. Firefox did not delete Flash cookies (and regular cookies) for a few restart cycles (maybe the FF instance did not shut down properly, never checked), but now it does.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.