{"push_id":629742240,"size":2,"distinct_size":2,"ref":"refs/heads/feature/seal-handle-scope","head":"004cba0027d6b584893bf9bf51ced1b0a9cf97b7","before":"88df3dc068127b7d3a4d91c86d7c45411e1d982f","commits":[{"sha":"7e2fa2135a48e3cc25b92767811a513147d6903e","author":{"email":"e39d94bae70283f13d24c278e04952d6dad9384b@indutny.com","name":"Fedor Indutny"},"message":"deps: backport 1f8555 from v8's upstream\n\nOriginal commit message:\n\n    api: introduce SealHandleScope\n\n    When debugging Handle leaks in io.js we found it very convenient to be\n    able to Seal some specific (root in our case) scope to prevent Handle\n    allocations in it, and easily find leakage.\n\n    R=yangguo\n    BUG=\n\n    Review URL: https://codereview.chromium.org/1079713002\n\n    Cr-Commit-Position: refs/heads/master@{#27766}\n\nShould help us identify and fix Handle leaks in core and user-space code.\n\nNOTE: Works only in Debug build now, but is still better than nothing.","distinct":true,"url":"https://api.github.com/repos/indutny/io.js/commits/7e2fa2135a48e3cc25b92767811a513147d6903e"},{"sha":"004cba0027d6b584893bf9bf51ced1b0a9cf97b7","author":{"email":"e39d94bae70283f13d24c278e04952d6dad9384b@indutny.com","name":"Fedor Indutny"},"message":"src: use global SealHandleScope\n\nHelps to find Handle leaks in Debug mode.","distinct":true,"url":"https://api.github.com/repos/indutny/io.js/commits/004cba0027d6b584893bf9bf51ced1b0a9cf97b7"}]}