• vogelheim's avatar
    Avoid data race when writing Shell::options.script_executed. · e045b78d
    vogelheim authored
    The race occurred when Workers were used. Since Workers call
    Shell::ExecuteString from a different thread, TSAN (correctly) flags
    this as a racy write. Solution would be to either synchronize the writes,
    or to 'lift' the write higher up in the call stack and only write the flag
    from the main thread. This implements this latter solution.
    
    These methods call Shell::ExecuteString, but do *not* set script_executed:
    - ExecuteInThread: Can only occur is JS has already been executed.
    - Shell::Load: Callback for JS; so JS has already been executed when
                   we get there.
    - Shell::RunShell: Interactive shell. We no longer need script_executed once
                       we're here.
    
    BUG=v8:4330
    LOG=N
    
    Review URL: https://codereview.chromium.org/1258303004
    
    Cr-Commit-Position: refs/heads/master@{#30003}
    e045b78d
d8.cc 79.2 KB