[Webkit-unassigned] [Bug 32618] [Chromium] Memory cache client calls should be disabled
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Dec 16 16:36:39 PST 2009
https://bugs.webkit.org/show_bug.cgi?id=32618
--- Comment #5 from Alexander Pavlov (apavlov) <apavlov at chromium.org> 2009-12-16 16:36:39 PST ---
(In reply to comment #3)
> (From update of attachment 44994 [details])
> What is a memoryCacheClientCall? Seems the ChangeLog might want to mention
> why we're disabling this. In general the change seems fine.
Eric, does mentioning the reasons similar to those in my original description
for this bug seem fine with you?
Basically, the active code path with memoryCacheClientCallsEnabled == true
creates duplicate resource IDs for cached resources that are loaded in a way
similar to "(new Image()).src = 'foo.png'" (I'm afraid to touch the solid
ground of this behavior as it stems from the JavaScript VM handling DOM, but it
seems Safari will exhibit the same bug as Chromium, without disabling the
AforeMentionedCalls.)
--
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