Closed Bug 789939 Opened 12 years ago Closed 8 years ago

Figure out why the doom list usually gets entries stuck in it for the life of the browser

Categories

(Core :: Networking: Cache, defect)

Product:
Core
Component:
Networking: Cache
Platform:
x86_64
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: bbondy, Unassigned)

References

Details

(Whiteboard: [Snappy:p2]) 

Sometimes the doom list remains un-empty until browser shutdown when we call ClearDoomList.  It is only safe to flush the cache though when the doom list is empty. 

In bug 105843 we want to start flushing the cache after it has been inactive for 3 seconds. 

This bug is to figure out why the doom list is getting an entry stuck in it. 
One way to reproduce this is to sign into twitter. You have to first be signed out. 

In that case, the key for the stuck entry is:
{mData=0x136fb9a8 "HTTP:https://twitter.com/" mLength=25 mFlags=5 }
Summary: Refine telemetry data for how much cache corruption reduction plan would help → Figure out why the doom list usually gets entries stuck in it for the life of the browser
Whiteboard: [Snappy] → [Snappy:p2]
Assignee: netzen → nobody
new cache code now
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.