VirtualAlloc fails with following error "ERROR_COMMITMENT_LIMIT 1455 (0x5AF
) The paging file is too small for this operation to complete."
Any Idea how this limit can be increased?
On Tuesday, March 15, 2016 at 3:10:29 PM UTC+5:30, tuma...@gmail.com wrote:
>
> I am using 64 bit build. This
I am using 64 bit build. This issue is reproducible in Windows machine. I
tried in MAC 64 bit build, it runs fine until it reaches the limit easily.
Steps to reproduce it in chrome browser (64bit):
1. launch from command line with args --js-flags="--max-old-
space-size=1"
2. use chrome
it means that the process ran out of memory. ~3GB sounds like you're
running a 32bit build?
On Tue, Mar 15, 2016 at 5:49 AM wrote:
> Exactly It fails in committing memory in VirtualAlloc (in file
> platform-win32.cc).
>
> bool VirtualMemory::CommitRegion(void* base, size_t
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)) {
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;
Is configuring the size via the ResourceConstraint class not covering your
use case?
On Fri, Mar 11, 2016, 5:14 PM wrote:
> Hi,
>
> We need to increase the V8 heap size limit for certain case. Can some one
> please point me the source code where we can change this limit?
>
Hi,
We need to increase the V8 heap size limit for certain case. Can some one
please point me the source code where we can change this limit?
Regards,
T. Umapathy
--
--
v8-dev mailing list
v8-dev@googlegroups.com
http://groups.google.com/group/v8-dev
---
You received this message because