1. 01 Sep, 2015 1 commit
  2. 14 Jul, 2015 1 commit
    • binji's avatar
      d8 workers: Fix transferring SharedArrayBuffer to multiple Workers. (try 2) · 5a9722b2
      binji authored
      Note: the previous try was reverted for occasional flaky tests. This continued
      after the revert, and should be fixed by
      https://codereview.chromium.org/1226143003.
      
      Previously, the serialization code would call Externalize for every transferred
      ArrayBuffer or SharedArrayBuffer, but that function can only be called once. If
      the buffer is already externalized, we should call GetContents instead.
      
      Also fix use-after-free bug when transferring ArrayBuffers. The transferred
      ArrayBuffer must be internalized in the new isolate, or be managed by the
      Shell. The current code gives it to the isolate externalized and frees it
      immediately afterward when the SerializationData object is destroyed.
      
      BUG=chromium:497295
      R=jarin@chromium.org
      LOG=n
      
      Review URL: https://codereview.chromium.org/1223813008
      
      Cr-Commit-Position: refs/heads/master@{#29658}
      5a9722b2
  3. 07 Jul, 2015 1 commit
  4. 06 Jul, 2015 1 commit
    • binji's avatar
      Fix bug when transferring SharedArrayBuffer to multiple Workers. · dd7962bf
      binji authored
      Previously, the serialization code would call Externalize for every transferred
      ArrayBuffer or SharedArrayBuffer, but that function can only be called once. If
      the buffer is already externalized, we should call GetContents instead.
      
      Also fix use-after-free bug when transferring ArrayBuffers. The transferred
      ArrayBuffer must be internalized in the new isolate, or be managed by the
      Shell. The current code gives it to the isolate externalized and frees it
      immediately afterward when the SerializationData object is destroyed.
      
      BUG=chromium:497295
      R=jarin@chromium.org
      LOG=n
      
      Review URL: https://codereview.chromium.org/1215233004
      
      Cr-Commit-Position: refs/heads/master@{#29499}
      dd7962bf
  5. 01 Jul, 2015 1 commit
  6. 30 Jun, 2015 1 commit
  7. 25 Jun, 2015 1 commit
    • binji's avatar
      Fix cluster-fuzz regression when getting message from Worker · 28b0129b
      binji authored
      The issue is that Worker.prototype.terminate was deleting the C++ Worker
      object, and then Worker.prototype.getMessage was trying to read messages from
      the queue.
      
      The simplest solution is to keep workers in a zombie state when they have been
      terminated. They won't be reaped until Shell::CleanupWorkers is called.
      
      I've also fixed some threading issues with Workers:
      
      * Workers can be created by another Worker, so the Shell::workers_ variable
      must be protected by a mutex.
      
      * An individual Worker can typically only be accessed by the isolate that
      created it, but the main thread can always terminate it, so the Worker::state_
      must be accessed in a thread-safe way.
      
      BUG=chromium:504136
      R=jochen@chromium.org
      LOG=n
      
      Review URL: https://codereview.chromium.org/1208733002
      
      Cr-Commit-Position: refs/heads/master@{#29306}
      28b0129b
  8. 26 Jun, 2013 1 commit
  9. 22 Jan, 2013 1 commit
  10. 19 Jan, 2012 1 commit
  11. 13 Jan, 2012 1 commit
  12. 27 Nov, 2009 1 commit
  13. 23 Oct, 2009 1 commit
  14. 20 Oct, 2009 1 commit
  15. 04 Mar, 2009 1 commit
  16. 26 Sep, 2008 1 commit
  17. 09 Sep, 2008 1 commit
  18. 22 Aug, 2008 1 commit
    • christian.plesner.hansen's avatar
      Included mjsunit JavaScript test suite and C++ unit tests. · c42f5829
      christian.plesner.hansen authored
      In the shell sample don't print the result of executing a script, only
      evaluating expressions.
      
      Fixed issue when building samples on Windows using a shared V8
      library.  Added visibility option on Linux build which makes the
      generated library 18% smaller.
      
      Changed build system to accept multiple build modes in one build and
      generate seperate objects, libraries and executables for each mode.
      
      Removed deferred negation optimization (a * -b => -(a * b)) since this
      visibly changes operand conversion order.
      
      Improved parsing performance by introducing stack guard in preparsing.
      Without a stack guard preparsing always bails out with stack overflow.
      
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      c42f5829
  19. 03 Jul, 2008 1 commit