[Webkit-unassigned] [Bug 98508] [WK2] Icons are retained but never released
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Oct 11 11:56:35 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=98508
--- Comment #7 from Brady Eidson <beidson at apple.com> 2012-10-11 11:57:16 PST ---
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > The problem in practice is that you end up with favicons in the database that you don't want, not a big issue, of course.
> >
> > I'm confused. Can you more explicitly spell out how - after the database pruning on the next launch - you would end up with icons you don't want?
>
> hmm, what icons are pruned on next launch? this is the test I have done:
>
> 1.- Delete the database
> 2.- Load two pages in MiniBrowser and retain the icon for one but release for the other
> 3.- Close MiniBrowser, both icons are in the database.
> 4.- Open MiniBrowser and load only the page that I retained the icon, to make sure I don't retain the released icon.
> 5.- Close MiniBrowser, both icons are in the database.
>
> Without retaining/releasing the icons in HistoryItem, the released icon is not in the database when I close MiniBrowser.
The design for this scenario is that unretained icons get cleaned up on the next launch. That's where something is going wrong here, around step 4 + 5.
Whats the delayDatabaseCleanup/allowDatabaseCleanup situation on the next launch?
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list