bnoordhuis/node-profiler

warnings while using nprof

mikedeboer opened this issue · 11 comments

This might be due to an out-of-date nprof that you have in this repo?

Code move event for unknown code: 0x2f80381d30c0
line 571441: unknown command: markcompact
line 571442: unknown command: delete
...
line 1040915: unknown command: check-maps-depth
line 1041743: unknown command: scavenge
line 1041744: unknown command: new

in no particular order from a generated v8.log file being processed.

Yes, or too new. With what version of node and node-profiler are you seeing this?

0.6.19, might also cause not to show a call profile.

profiler version 1.1.0

I think it's a matter of nprof being too new, not much has changed upstream. Still, can you try the update-nprof branch?

with that branch I get:

line 4147: unknown code state: 0x2e170abe27f0
Code move event for unknown code: 0x2f80381fc6e0
Code move event for unknown code: 0x2f80381db380
Code move event for unknown code: 0x2f80381d7e20
Code move event for unknown code: 0x2f80381d50c0
Code move event for unknown code: 0x2f80381d30c0
...

Maybe the V8 people simply forgot to upgrade the profiler tools... can you try the downgrade-nprof branch? If that doesn't fix it, I'll have to patch V8.

I tried, but I'm back to the scenario of version 1.1.0 (the version of profiler in npm)... in both branches I get no call profile, which is actually the most useful for me potentially!

Okay, noted. Can you upload the v8.log somewhere?

plz check your skype for a link to a gist ;)

Okay, this should be fixed per df1fc75.

You may still get a warning or two - there's a function called <ul id="files">.files.map.icon /foo/bar/baz (probably some string/function mapping). The V8 in 0.6 doesn't escape the function name properly but that's fixed in v0.8.