Skip to content

next: Update v8 to 4.3.61.27 - #1909

Closed
targos wants to merge 2 commits into
nodejs:nextfrom
targos:next-v8-27
Closed

next: Update v8 to 4.3.61.27#1909
targos wants to merge 2 commits into
nodejs:nextfrom
targos:next-v8-27

Conversation

@targos

Copy link
Copy Markdown
Member

targosand others added 2 commits June 6, 2015 08:59
Original commit message:
api: introduce SealHandleScope
When debugging Handle leaks in io.js we found it very convenient to be
able to Seal some specific (root in our case) scope to prevent Handle
allocations in it, and easily find leakage.
R=yangguo
BUG=
Review URL: https://codereview.chromium.org/1079713002
Cr-Commit-Position: refs/heads/master@{nodejs#27766}
Should help us identify and fix Handle leaks in core and user-space code.
NOTE: Works only in Debug build now, but is still better than nothing.
PR-URL: nodejs#1395
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@mscdexmscdex added the v8 engine Issues and PRs related to the V8 dependency. label Jun 6, 2015
@Fishrock123

Copy link
Copy Markdown
Contributor

cc @bnoordhuis

@trevnorris

Copy link
Copy Markdown
Contributor

Not near my laptop or would do it myself, but let's kick off a CI. Change looks pretty straight forward.

@cjihrig

Copy link
Copy Markdown
Contributor

@targos

Copy link
Copy Markdown
MemberAuthor

New URL: https://jenkins-iojs.nodesource.com/view/iojs/job/iojs+any-pr+multi_old/794/
Anything possibly related in the failing tests?

@trevnorris

Copy link
Copy Markdown
Contributor

@chrisdickinson Please always leave a reason for closing.

@trevnorristrevnorris reopened this Jun 17, 2015
@targos

Copy link
Copy Markdown
MemberAuthor

I'll close it myself in favor of the upgrade to V8 4.4: #1807 (comment)

@targostargos closed this Jun 19, 2015
@chrisdickinson

Copy link
Copy Markdown
Contributor

Ah, this was likely automatically closed by GitHub when I recut next. Sorry I missed it.

On Jun 16, 2015, at 9:27 PM, Trevor Norris notifications@github.com wrote:

@chrisdickinson Please always leave a reason for closing.


Reply to this email directly or view it on GitHub.

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

v8 engineIssues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants

@targos@Fishrock123@trevnorris@cjihrig@chrisdickinson@mscdex@indutny