Issue 2114 in v8: GetHeapValue returns invalid values

[codesite...@google.com]

Status: New
Owner: ----

New issue 2114 by k...@skomski.com: GetHeapValue returns invalid values
http://code.google.com/p/v8/issues/detail?id=2114

When I use the returned value from `GetHeapValue` I often get a
segmentation fault.

I call it from a node.js module.
https://github.com/Skomski/v8-profiler/blob/unstable/src/graph_node.cc#L77

What steps will reproduce the problem?

npm install https://github.com/Skomski/v8-profiler/tarball/v3.7.1
node test.js


Attachments:
debug.log 16.2 KB
test.js 186 bytes

[codesite...@google.com]

Comment #1 on issue 2114 by k...@skomski.com: GetHeapValue returns invalid
values
http://code.google.com/p/v8/issues/detail?id=2114

(No comment was entered for this change.)

Attachments:
test.js 185 bytes

[codesite...@google.com]

Comment #2 on issue 2114 by seth.ide...@gmail.com: GetHeapValue returns
invalid values
http://code.google.com/p/v8/issues/detail?id=2114

I had the same problem and wrote a function getHeapValueSafe which only
returns values for nodes which don't segfault. Not sure if it is too
conservative. I invite comment. You can get the code at
https://github.com/seth4618/v8-profiler

[codesite...@google.com]

Updates:
Cc: loi...@chromium.org alex...@chromium.org yu...@chromium.org

Comment #3 on issue 2114 by mikhail.naganov: GetHeapValue returns invalid
values
http://code.google.com/p/v8/issues/detail?id=2114

[codesite...@google.com]

Comment #4 on issue 2114 by yu...@chromium.org: GetHeapValue returns
invalid values
http://code.google.com/p/v8/issues/detail?id=2114

You are likely calling GetHeapValue on a V8 internal object that cannot be
exposed though the V8 public API.

[codesite...@google.com]

Updates:
Status: WorkingAsIntended

Comment #5 on issue 2114 by habl...@chromium.org: GetHeapValue returns
invalid values
https://code.google.com/p/v8/issues/detail?id=2114

Update done during clean-up of issue tracker.

Please check if you are doing the stuff mentioned in #4. If the problem
still persists please reopen this issue.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings