RESOLVED FIXED 109039
[V8] Rename isolated() to getWorld(), rename worldForEnteredContextIfIsolated() to worldForEnteredContext()
https://bugs.webkit.org/show_bug.cgi?id=109039
Summary [V8] Rename isolated() to getWorld(), rename worldForEnteredContextIfIsolated...
Kentaro Hara
Reported 2013-02-06 03:54:27 PST
For naming consistency, rename isolated() to getWorld() and rename worldForEnteredContextIfIsolated() to worldForEnteredContext().
Attachments
Patch (8.97 KB, patch)
2013-02-06 03:56 PST, Kentaro Hara
no flags
patch for landing (9.72 KB, patch)
2013-02-07 00:46 PST, Kentaro Hara
haraken: commit-queue-
Kentaro Hara
Comment 1 2013-02-06 03:56:57 PST
WebKit Review Bot
Comment 2 2013-02-06 05:39:10 PST
Comment on attachment 186816 [details] Patch Attachment 186816 [details] did not pass cr-linux-debug-ews (chromium-xvfb): Output: http://queues.webkit.org/results/16388281
Adam Barth
Comment 3 2013-02-06 10:26:20 PST
Comment on attachment 186816 [details] Patch Looks like the cr-linux-debug bot is unhappy with this patch.
Kentaro Hara
Comment 4 2013-02-07 00:46:29 PST
Created attachment 187009 [details] patch for landing
Kentaro Hara
Comment 5 2013-02-07 05:40:20 PST
Comment on attachment 187009 [details] patch for landing A patch which this patch depends on was rolled out.
Kentaro Hara
Comment 6 2013-02-10 20:16:37 PST
Dan Carney
Comment 7 2013-02-27 03:55:38 PST
This change makes no sense. The function on DOMWrapperWorld only returns an isolated world. It does that for performance. This leads to semantic ambiguity like in V8GCController::minorGCPrologue: DOMWrapperWorld* world = worldForEnteredContextWithoutContextCheck(); if (world && world->isMainWorld()) { the branch will never be taken and minor gc is disabled because of this. Please consider this reverting this renaming.
Kentaro Hara
Comment 8 2013-02-27 07:33:56 PST
ah... This was a big mistake. Let me revert them. Because we're limiting the number of nodes handled by each minor GC to 10000, I couldn't detect the performance regression by Dromaeo/dom-modify...
Note You need to log in before you can comment on or make changes to this bug.