Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(114)

Issue 2783203002: [wrapper-tracing] Emite write barrier upon associating a wrapper (Closed)

Created:
3 years, 8 months ago by Michael Lippautz
Modified:
3 years, 8 months ago
Reviewers:
Michael Moss
CC:
chromium-reviews, dimu, govind
Target Ref:
refs/branch-heads/2987
Project:
chromium
Visibility:
Public.

Description

[wrapper-tracing] Emite write barrier upon associating a wrapper Whenever we assign a reference that should be traced into V8 we need to emit a write barrier. We automatically emit write barriers for TraceWrapperv8Reference. However, we still use a regular (weak) Persistent in ScriptWrappable, so we need to emit the barrier there manually. A follow up should convert the reference in ScriptWrappable to TraceWrapperv8Reference. BUG=chromium:702490 Review-Url: https://codereview.chromium.org/2759243002 Cr-Commit-Position: refs/heads/master@{#458357} (cherry picked from commit a2011780ffefd6f9c120b80651015b3f6646244b) Review-Url: https://codereview.chromium.org/2783203002 . Cr-Commit-Position: refs/branch-heads/2987@{#896} Cr-Branched-From: ad51088c0e8776e8dcd963dbe752c4035ba6dab6-refs/heads/master@{#444943} Committed: https://chromium.googlesource.com/chromium/src/+/24f8804aa139486723395483bda7015d3c57e1b2

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+21 lines, -2 lines) Patch
M third_party/WebKit/Source/bindings/core/v8/ScriptWrappable.h View 2 chunks +2 lines, -0 lines 0 comments Download
M third_party/WebKit/Source/bindings/core/v8/ScriptWrappableVisitor.h View 3 chunks +6 lines, -1 line 0 comments Download
M third_party/WebKit/Source/bindings/core/v8/ScriptWrappableVisitor.cpp View 3 chunks +12 lines, -1 line 0 comments Download
M third_party/WebKit/Source/core/dom/MutationCallback.h View 1 chunk +1 line, -0 lines 0 comments Download

Messages

Total messages: 7 (3 generated)
Michael Lippautz
Committed patchset #1 (id:1) manually as 24f8804aa139486723395483bda7015d3c57e1b2.
3 years, 8 months ago (2017-03-30 14:11:30 UTC) #2
Michael Moss
I believe this is causing compile failures on the official builders, e.g.: https://uberchromegw.corp.google.com/i/official.desktop/builders/win-pgo/builds/1059/ src\third_party\webkit\source\bindings\core\v8\scriptwrappablevisitor.h(11): fatal ...
3 years, 8 months ago (2017-03-31 01:02:57 UTC) #4
Michael Moss
On 2017/03/31 01:02:57, Michael Moss wrote: > I believe this is causing compile failures on ...
3 years, 8 months ago (2017-03-31 01:06:40 UTC) #5
Michael Lippautz
3 years, 8 months ago (2017-03-31 07:04:04 UTC) #6
Message was sent while issue was closed.
On 2017/03/31 01:06:40, Michael Moss wrote:
> On 2017/03/31 01:02:57, Michael Moss wrote:
> > I believe this is causing compile failures on the official builders, e.g.:
> > 
> >
>
https://uberchromegw.corp.google.com/i/official.desktop/builders/win-pgo/buil...
> > 
> > src\third_party\webkit\source\bindings\core\v8\scriptwrappablevisitor.h(11):
> > fatal error C1083: Cannot open include file: 'platform/heap/VisitorImpl.h':
No
> > such file or directory
> 
> Looks like the failure was already noted in crbug.com/706985. Not sure why it
> hasn't been reverted yet.

Thanks, it merged without a problem back to M58 and I wasn't aware of any
refactoring happening between M57 and M58 in that area. Will investigate.

Powered by Google App Engine
This is Rietveld 408576698