Re: [v8-dev] How to increase JS Heap size limit?

Exactly It fails in committing memory in VirtualAlloc (in file platform-win32.cc). bool VirtualMemory::CommitRegion(void* base, size_t size, bool is_executable) { int prot = is_executable ? PAGE_EXECUTE_READWRITE : PAGE_READWRITE; if (NULL == VirtualAlloc(base, size, MEM_COMMIT, prot)) {

[v8-dev] Fwd: Us congress hearing of maan alsaan Money laundry قضية الكونغجرس لغسيل الأموال للمليادير معن الصانع

YouTube videos of U.S. Congress money laundering hearing of Saudi Billionaire " Maan Al sanea" with *bank of America* and The owner of Saad Hospital and Schools in the Eastern Province in *Saudi Arabia* and the Chairman of the Board of Directors of Awal Bank in *Bahrain*

Re: [v8-dev] How to increase JS Heap size limit?

I tried with --js-flags="--max-old-space-size=1" while launching my app (using CEF). And used below script to check (from https://bugs.chromium.org/p/v8/issues/detail?id=847) (function () { function tree (n, m) { if (n > 0) { var a = new Array(m); for (var i = 0; i < m;

[v8-dev] Re: Undestading V8 full-codegen compilation pipeline

You can checkout my blog post: http://mshockwave.blogspot.tw/2016/01/quick-note-v8-javascript-engines-first.html Although it focus on the baseline compiler but it may helps. Cheers, McClane dima...@gmail.com於 2016年3月2日星期三 UTC+8下午7時53分48秒寫道： > > Hello! > > I just want to understand how v8 compile

Re: [v8-dev] CVE-2016-1007, CVE-2016-1009

CVEs are very specific to the product they refer to - usually, they don't affect other products that don't use the exact product and version referenced in the CVE. So, no, V8 is not affected by those two CVEs Best Jochen On Mon, Mar 14, 2016, 12:57 AM Barry Dawson