Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Upgrade from 3.3 to 3.9 causes code to segfault
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
BrianG  
View profile  
 More options Apr 10 2012, 7:02 pm
From: BrianG <briangef...@gmail.com>
Date: Tue, 10 Apr 2012 16:02:20 -0700 (PDT)
Local: Tues, Apr 10 2012 7:02 pm
Subject: Upgrade from 3.3 to 3.9 causes code to segfault
Hello All,

I'm trying to understand why the following code would break on an
upgrade from v8 3.3 to 3.9. The code segfaults when creating a new
handle_scope, if I remove the handle scope inside the while loop it
will run but will quickly run out of memory. The segfault i'm
receiving is:

#0  0x00007fffecdc8942 in
v8::internal::HandleScope::DeleteExtensions(v8::internal::Isolate*) ()
from
#1  0x00007fffecd43117 in render::engine::(anonymous
namespace)::threadLoaded (data=<value optimized out>) at engine.cpp:
411
#2  0x00000000004b857c in ink_thread_trampoline (data=<value optimized
out>) at InkIOCoreAPI.cc:116
#3  0x0000003b93a077e1 in start_thread () from /lib64/libpthread.so.0
#4  0x0000003b936e68ed in clone () from /lib64/libc.so.6

The code is as follows:

  v8::Isolate* isolate = v8::Isolate::New();
  v8::Isolate::Scope isolate_scope(isolate); // enter isolate
  v8::Locker locker(isolate);

  v8::HandleScope handle_scope;
  v8::Persistent<v8::Context> context = v8::Context::New();
  v8::Context::Scope context_scope(context); // enter base context

  // do some stuff

  while (true) {
    // Create a new context
    v8::HandleScope per_request_handle_scope;
    v8::Persistent<v8::Context> per_request_context =
v8::Context::New();
    v8::Context::Scope
per_request_context_scope(per_request_context); // enter context

      // do some stuff

    per_request_context.Dispose(); // As always, dispose of the
context..
  } /*


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Oleg Efimov  
View profile   Translate to Translated (View Original)
 More options Apr 29 2012, 4:16 pm
From: Oleg Efimov <efimo...@gmail.com>
Date: Sun, 29 Apr 2012 13:16:32 -0700 (PDT)
Local: Sun, Apr 29 2012 4:16 pm
Subject: Re: Upgrade from 3.3 to 3.9 causes code to segfault

Have you fixed this issue, Brian? I'm also interesting on solution.

среда, 11 апреля 2012 г., 3:02:20 UTC+4 пользователь BrianG написал:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »