| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Does doc/iojs.1 also need to be modified? |
Sorry, something went wrong.
|
I am not able to understand why we need the whitespace changes. |
Sorry, something went wrong.
|
@thefourtheye it was to keep 2 spaces between the switch and the description and keeping all of the descriptions aligned |
Sorry, something went wrong.
|
@ofrobots i can but I saw that --trace-sync-io was not in there either |
Sorry, something went wrong.
|
@bmeck Ah, I see what you are saying now. " --track-heap-objects track heap object allocations for heap snapshots\n", correct? Not a v8 expert, but the changes look straight-forward. |
Sorry, something went wrong.
There was a problem hiding this comment.
Shouldn't we explicitly set this to False, in the else part?
Sorry, something went wrong.
There was a problem hiding this comment.
none of the other switches work that way
Sorry, something went wrong.
There was a problem hiding this comment.
👍
Sorry, something went wrong.
There was a problem hiding this comment.
Does it even need to be exposed to JS land?
(I guess the same question applies to .traceSyncIO, /cc @trevnorris.)
Sorry, something went wrong.
There was a problem hiding this comment.
Yup. You're right. I can't think of a useful case to expose either of them to JS.
Sorry, something went wrong.
There was a problem hiding this comment.
Good to know. @bmeck Can you remove the .trackHeapObjects property (and .traceSyncIO in a separate commit if you want)?
Sorry, something went wrong.
|
@bnoordhuis removed trackHeapObjects from process, separate PR for traceSyncIO #2143 |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Do we need a test for this? |
Sorry, something went wrong.
|
@thefourtheye node itself does not include a way to dump heap snapshots, we could write one up but it would be akin to including node-heapdump in core. |
Sorry, something went wrong.
- This makes v8 add .trace_function_info to the serialized form of snapshots from v8::HeapSnapshot::Serialize - .trace_funciton_info combined with .trace_node in snapshots tells the JS location that allocated a specific object
- This makes v8 add .trace_function_info to the serialized form of snapshots from v8::HeapSnapshot::Serialize - .trace_funciton_info combined with .trace_node in snapshots tells the JS location that allocated a specific object PR-URL: #2135 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Trevor Norris <trev.norris@gmail.com>
|
Tagged as semver-minor, 2.4.0 ho! :) |
Sorry, something went wrong.
Notable changes * src: Added a new `--track-heap-objects` flag to track heap object allocations for heap snapshots (Bradley Meck) nodejs#2135. * readline: Fixed a freeze that affected the repl if the keypress event handler threw (Alex Kocharin) nodejs#2107. * npm: Upgraded to v2.13.0, release notes can be found in https://github.com/npm/npm/releases/tag/v2.13.0 (Forrest L Norvell) nodejs#2152. PR-URL: nodejs#2189
| Back | FazBrowse Home | New Git URL |
Right now we do not have a way to start iojs with heap object tracking.
Calling v8::Profiler::StartTrackingHeapObjects after node has started up will not include the reference info for objects in node core. This can be seen by running node-heapdump with the flag turned on. This information is useful for debugging tools and would be visible in Chrome DevTools in the same way that "Record heap allocation stack traces" functions from the DevTools settings pane.