Hi,
Also, when we throw the exception as below by creating new exception object
in FatalProcessOutOfMemory() ,Invoke() is not returned back out of V8
execution.
Please clarify what API can be called for the same, so that we come out of
V8.Execute().
Regards,
Madan
--
--
v8-users mailing l
Hi,
We have the issue number 1181417 mentioned as "To be fixed" at the place of
calling FatalProcessOutOfMemory() in heap-inl.h. Please clarify do we have
any API/function/exception can be called/thrown from here, so it terminate
the V8::Execute call and get returned. Thanks.
Regards,
Madan
>
> Hi,
>
In this case, do we have any API/exception that can be called back instead
of terminating and show an pop up in the client side, indicating memory is
unavailable instead of crashing?. Please let me know.
Regards,
Madan
--
--
v8-users mailing list
v8-users@googlegroups.com
http:/
Hey,
I started using Viber. It’s a cool app that lets you call and text for free.
Viber is easy to use and works just like a regular phone:
• No need to create a username or log in
• Works with your phone’s existing contact list
• Shows which of your contacts already has it
Get Viber: www.viber.
What exactly are you trying to accomplish with this?
Copying a context would be a huge operation, if it's possible at all (I
don't think it is).
You are almost certainly better off encapsulating the state you want in
JSON or through some API you come up with yourself, and then loading that
in
Which flags does --trace incorporate? Or in otherwords, where is the
printfs coming from: I don't see trace as an option on the d8 help list,
but it does work:
I see the function name "test" being printed out: (e.g.)
1: ~+51(this=0x24e1a20144b9 ) {
and the output of the function and its ty
What about making copy/clone of context?
4 бер. 2015 09:52, користувач "Yang Guo" написав:
>
> A context is too deeply entangled into the isolate it belongs to, so
moving the context but not the isolate is basically impossible with the
current V8.
>
>
> On Sunday, March 1, 2015 at 9:29:49 PM UTC+
Thanks much for the valuable information :). If i have any doubts, i will
get back.
Regards,
Madan
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You received this message because you are subscribed to the Google Groups
"v8-users" group.
To
Well, that obviously depends on how much memory the device has, and on the
limits you've set. Whatever limit is hit first (physical or configured)
determines when execution is terminated.
On Thu, Mar 5, 2015 at 2:22 PM, madana gopal
wrote:
> Thanks for the information.
>
> Just to confirm my und
Thanks for the information.
Just to confirm my understanding, if we are seeing allocation failure even
after increasing the old space and young space size, then the device memory
increase is the only solution to solve the problem in this case?. Please
clarify.
Thanks.
Regards,
Madan
--
--
Unrelated.
The idea of the snapshot is to perform most of the initialization (of the
heap, builtins, ...) that has to happen on every startup at build time, and
package the result as part of the binary, to significantly increase startup
speed. It shouldn't affect memory consumption.
On Thu, Mar 5
Hi,
Thanks much for the details. I have one small doubt. I saw one option
v8_use_snapshot but couldn't understand. Could you please tell what is it
and anywhere relate to our current problem?.
Regards,
Madan
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/grou
Thanks for the trace.
It does look like the GC is working extra hard (very fast marking speed,
old-space GC every ~250ms) because it realizes that it's close to the
memory limit; unfortunately it doesn't find many dead objects (see the
"Mark-sweep" line: memory usage only went from 129.9 to 129.5 M
Hi,
One more information. If we increase the old/young space size , allocation
failure is not happening immediately, but after sometime.Probably due to
memory increase, it is taking some more time it seems. Please correct if
this understanding is wrong.
Regards,
Madan
--
--
v8-users mailin
On Thu, Mar 5, 2015 at 11:20 AM, Ben Noordhuis wrote:
> If I were the OP, I'd experiment with -O2 and -Os and fastidiously
> benchmark with perf.
>
-O2/-Os might make sense, but I don't think -O0 will.
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-use
On Thu, Mar 5, 2015 at 11:11 AM, madana gopal
wrote:
> Hi,
>
> Thanks much for the explanation.
>
> 1, We are seeing more time is being taken during the execution of
> charCodeAt() function (in Encoding the URI) flatten call and more new raw
> byte strings are being allocated. Our low memory dev
On Thu, Mar 5, 2015 at 10:22 AM, Jakob Kummerow wrote:
> On Thu, Mar 5, 2015 at 7:44 AM, madana gopal
>> 2,Also, is it good to disable optimization for less memory device.
>
> I don't think that would be very beneficial.
>
>> From which file i can make the optimization to O0?. Please clarify.
>
>
Hi,
Thanks much for the explanation.
1, We are seeing more time is being taken during the execution of
charCodeAt() function (in Encoding the URI) flatten call and more new raw
byte strings are being allocated. Our low memory device is not able to
allocate much memory in young space and many
On Thu, Mar 5, 2015 at 7:44 AM, madana gopal
wrote:
> Hi,
>
> This is the doubt, i have regarding configuring V8 for low memory device.
>
> 1, When we run web pages with heavy data in javascript, old data space is
> getting occupied so quickly, since the young generation to space is lesser.
> Als
19 matches
Mail list logo
