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=10000"
2. use chrome developer tools to run the below script from console.
(function () {
function tree (n, m) {
if (n > 0) {
var a = new Array(m);
for (var i = 0; i < m; i++) a[i] = tree(n - 1, m);
return a;
}
}
var trees = [];
while (true) trees.push(tree(15, 2));
})();
On Tuesday, March 15, 2016 at 1:55:33 PM UTC+5:30, Jochen Eisinger wrote:
>
> 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 <[email protected] <javascript:>> wrote:
>
>> 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)) {
>> return false;
>> }
>> return true;
>> }
>>
>> Anybody knows whats going wrong here?
>>
>>
>> On Monday, March 14, 2016 at 8:54:43 PM UTC+5:30, [email protected]
>> wrote:
>>>
>>> I tried with --js-flags="--max-old-space-size=10000" 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; i++) a[i] = tree(n - 1, m);
>>> return a;
>>> }
>>> }
>>>
>>> var trees = [];
>>> while (true) trees.push(tree(15, 2));
>>> })();
>>>
>>>
>>> *After some time, the allocation in below line (in src\heap\spaces.cc
>>> PagedSpace::Expand()) fails and render process is crashing (memory usage
>>> was around 3GB +).*
>>>
>>> *------------------------------------------------------------------------------------------------------------------------------------------------*
>>>
>>>
>>> Page* p = heap()->isolate()->memory_allocator()->AllocatePage(size, this,
>>>
>>> executable());
>>> if (p == NULL) return false;
>>>
>>>
>>>
>>>
>>> On Friday, March 11, 2016 at 9:47:29 PM UTC+5:30, Jochen Eisinger wrote:
>>>>
>>>> Is configuring the size via the ResourceConstraint class not covering
>>>> your use case?
>>>>
>>>> On Fri, Mar 11, 2016, 5:14 PM <[email protected]> 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?
>>>>>
>>>>> Regards,
>>>>> T. Umapathy
>>>>>
>>>>>
>>>>> --
>>>>> --
>>>>> v8-dev mailing list
>>>>> [email protected]
>>>>> http://groups.google.com/group/v8-dev
>>>>> ---
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "v8-dev" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to [email protected].
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> --
>> --
>> v8-dev mailing list
>> [email protected] <javascript:>
>> http://groups.google.com/group/v8-dev
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "v8-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups
"v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
