lukechilds/node - node - Gitea: Git with a cup of tea

Commit Graph

Author	SHA1	Message	Date
Fedor Indutny	a960d1707a	deps: backport 23f2736a from v8 upstream Original text: Fix corner case in x64 compare stubs. BUG=v8:2416 Review URL: https://codereview.chromium.org/11413087 fix #7528	11 years ago
Ben Noordhuis	67e078094b	deps: upgrade v8 to 3.25.30	11 years ago
Trevor Norris	8d6fa72d97	v8: upgrade to 3.24.35.22	11 years ago
Fedor Indutny	4d140746f0	deps: update v8 to 3.24.35.17	11 years ago
Fedor Indutny	1c7bf245dc	deps: update v8 to 3.24.40	11 years ago
Timothy J Fontaine	95b8a75d5e	v8: Upgrade to 3.22.24.19	11 years ago
Trevor Norris	f78e5df854	v8: upgrade to 3.22.24.17	11 years ago
Fedor Indutny	8803aa3af7	deps: update v8 to 3.22.24.9	11 years ago
jkummerow@chromium.org	39e2426b20	v8: backport fix for CVE-2013-{6639\|6640} Quoting CVE-2013-6639: The DehoistArrayIndex function in hydrogen-dehoist.cc in Google V8 before 3.22.24.7, as used in Google Chrome before 31.0.1650.63, allows remote attackers to cause a denial of service (out-of-bounds write) or possibly have unspecified other impact via JavaScript code that sets the value of an array element with a crafted index. Quoting CVE-2013-6640: The DehoistArrayIndex function in hydrogen-dehoist.cc in Google V8 before 3.22.24.7, as used in Google Chrome before 31.0.1650.63, allows remote attackers to cause a denial of service (out-of-bounds read) via JavaScript code that sets a variable to the value of an array element with a crafted index. Like 6b92a7, this is unlikely to affect node.js because it only runs local, trusted code. However, if there exists some module somewhere that populates an array index with remotely provided data this could very well be used to crash a remote server running node. Defense in depth and all. This is a backport of upstream commit r17801. Original commit log: Limit size of dehoistable array indices LOG=Y BUG=chromium:319835,chromium:319860 R=dslomov@chromium.org Review URL: https://codereview.chromium.org/74113002	11 years ago
Timothy J Fontaine	b73967e9a0	v8: upgrade to 3.22.24.5	11 years ago
Ben Noordhuis	f230a1cf74	v8: upgrade to 3.22.24 This commit removes the simple/test-event-emitter-memory-leak test for being unreliable with the new garbage collector: the memory pressure exerted by the test case is too low for the garbage collector to kick in. It can be made to work again by limiting the heap size with the --max_old_space_size=x flag but that won't be very reliable across platforms and architectures.	11 years ago
Timothy J Fontaine	a53c763c16	v8: upgrade 3.21.18.3	12 years ago
Timothy J Fontaine	85898d1967	v8: upgrade to 3.20.17.13 fixes #6235	12 years ago
Ben Noordhuis	14687ebfc0	Revert "deps: update v8 to 3.20.17.11" After the upgrade from 3.20.17.7 to 3.20.17.11, we've begun hitting random assertions in V8 in memory-constrained / GC-heavy situations. The assertions all seem to be related to heap allocations and garbage collection but apart from that, they're all over the place. This reverts commit `970bdccc38`.	12 years ago
Fedor Indutny	970bdccc38	deps: update v8 to 3.20.17.11 fix #6235	12 years ago
Fedor Indutny	a1cf3ada62	deps: update v8 to 3.20.17.7	12 years ago
Trevor Norris	26bc8db33f	v8: upgrade to 3.20.17	12 years ago
Ben Noordhuis	f69be329f0	v8: upgrade v8 to 3.20.14.1	12 years ago
Ben Noordhuis	2fc47ab10b	v8: upgrade v8 to 3.20.11	12 years ago
Ben Noordhuis	1bd711c8a0	v8: upgrade to v8 3.20.9	12 years ago
Trevor Norris	5777d7ab30	v8: upgrade to v8 3.20.7	12 years ago
Ben Noordhuis	704fd8f374	v8: upgrade to v3.20.2	12 years ago
Ben Noordhuis	6dd78074a3	v8: upgrade to v3.19.13	12 years ago
Trevor Norris	506fc4de1e	v8: upgrade to v3.19.3	12 years ago
Ben Noordhuis	7ee538ddfe	deps: upgrade v8 to 3.19.0	12 years ago
Ben Noordhuis	2f75785c01	deps: upgrade v8 to 3.18.4	12 years ago
isaacs	50624a50ee	V8: Upgrade to 3.18.1	12 years ago
Ben Noordhuis	9f682265d6	deps: upgrade v8 to 3.18.0	12 years ago
Ben Noordhuis	587e83c6d6	v8: upgrade to 3.17.16	12 years ago
Trevor Norris	83261e789e	deps: update v8 to 3.17.13	12 years ago
isaacs	81c278d58d	V8: Upgrade to 3.14.5.8	12 years ago
Ben Noordhuis	b15a10e7a0	deps: downgrade v8 to 3.14.5 V8 3.15 and newer have stability and performance issues. Roll back to a known-good version.	12 years ago
isaacs	0c2e5ec840	V8: Upgrade to 3.15.11.15	12 years ago
isaacs	8024252877	V8: Upgrade to 3.15.11.10	12 years ago
Fedor Indutny	d22bd9e3c4	deps: update v8 to 3.15.11.7	12 years ago
Fedor Indutny	0054264d88	v8: update to 3.15.11.5	12 years ago
Fedor Indutny	7b4d95a976	deps: update v8 to 3.15.11	12 years ago
isaacs	95c9305874	V8: Upgrade to 3.13.7.4	13 years ago
isaacs	29d12c7342	V8: Upgrade to 3.11.10.25	13 years ago
isaacs	3411a03dd1	V8: Upgrade to 3.13.7.1	13 years ago
Bert Belder	4899116d4b	v8: upgrade to 3.11.10.22	13 years ago
Bert Belder	2d9239359d	v8: upgrade to v3.11.10.19	13 years ago
isaacs	f4f0daa44d	V8: Upgrade to 3.11.10.17	13 years ago
Bert Belder	74872b0dc9	v8: upgrade to version 3.11.10.12	13 years ago
Bert Belder	6b26583e84	v8: upgrade to v3.11.10.10	13 years ago
mstarzinger@chromium.org	48893af7bb	Fix performance regression caused by r11202. R=erik.corry@gmail.com BUG=v8:2156,v8:2034 TEST=mjsunit/regress/regress-2156,mjsunit/regress/regress-2034 Review URL: https://chromiumcodereview.appspot.com/10539131 git-svn-id: https://v8.googlecode.com/svn/branches/bleeding_edge@11800 ce2b1a6d-e550-0410-aec6-3dcde31c8c00	13 years ago
Bert Belder	50464cd4f4	v8: upgrade to v3.11.10	13 years ago
isaacs	940a6863ea	Roll V8 back to 3.9.24.31	13 years ago
isaacs	46b09e4190	Roll V8 back to 3.10.8.13	13 years ago
isaacs	cbdf3393a2	Upgrade v8 to 3.11.7	13 years ago

1 2 3 4 5

202 Commits (73d9c0f903ae371cd5011af64c3a6f69a1bda978)