Does this still happen with the tip of any of the branches that are still
supported (3.22, 3.23, trunk)? 3.17.1 is a daily snapshot from ten months
ago, I don't think anyone will even begin to investigate that version.


On Thu, Dec 12, 2013 at 9:28 AM, <[email protected]> wrote:

> I have an object class with a NamedPropertyHandler. I can write in JS
>
>     for (var p in obj)
>     {
>           print(p);
>     }
>
> and find that some, *but not all*, of the properties returned by the
> NamedPropertyEnumerator are missing. Other properties
> added via prototypes and SetAccessor() still appear.
>
> I can call the Object::GetPropertyNames() method in C++ and see all of the
> property names.
> I can debug the V8 engine and see that at the end of
> Runtime_GetPropertyNamesFast() all
> of the property names are in the content array. But by the time the code
> gets to the for-in loop body some of the names
> are missing.
>
> My C++ code looks like
>
>        HandleScope  scope;
>        Local<Array> array;
>
>         array = Array::New(names.size());
>
>         for (size_t i = 0; i < names.size(); ++i)
>         {
>             array->Set(i, js::CastToJS(names[i]));     // does
> String::New()
>         }
>
>         return scope.Close(array);
>
>
> Am I confusing the memory management somehow?
>
>  --
> --
> v8-users mailing list
> [email protected]
> http://groups.google.com/group/v8-users
> ---
> You received this message because you are subscribed to the Google Groups
> "v8-users" 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/groups/opt_out.
>

-- 
-- 
v8-users mailing list
[email protected]
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" 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/groups/opt_out.

Reply via email to