Updates:
Status: Assigned
Owner: [email protected]
Comment #6 on issue 2999 by [email protected]:
test-cpu-profiler/CollectCpuProfile fails flakily.
http://code.google.com/p/v8/issues/detail?id=2999
The issue is caused by CodeCreateEvent's are missing ReleaseNoFrameRanges
info.
Here's the sample I managed to hunt down.
0 pc_off: -1 (root) 0 #1
6686 pc_off: 113 start 18 #3 no reason
4897 pc_off: 337 foo 18 #5 TryCatchStatement
24516 pc_off: 188 delay 18 #6 TryCatchStatement
14809 pc_off: 208 loop 18 #7 no reason
0 pc_off: 56 bar 18 #9 no reason
154 pc_off: 188 delay 18 #10 TryCatchStatement
204 pc_off: 370 loop 18 #11 no reason
0 pc_off: 56 baz 18 #12 no reason
113 pc_off: 188 delay 18 #13 TryCatchStatement
152 pc_off: 370 loop 18 #14 no reason
1 pc_off: 337 foo 18 #4 TryCatchStatement 0xb9064655acf
0xb9064655066 (nil) (nil) (nil)
1812 pc_off: 0 (program) 0 #2
83029 pc_off: 0 (garbage collector) 0 #8
The point of interest is a single sample of foo hanging right at (root).
The call stack is:
0xb9064655acf
0xb9064655066
which translates into:
--- Code ---
source_position = 321
kind = FUNCTION
name = foo
Instructions (size = 424)
0xb9064655ac0 0 488b4c2408 REX.W movq rcx,[rsp+0x8]
0xb9064655ac5 5 493b4da8 REX.W cmpq rcx,[r13-0x58]
0xb9064655ac9 9 750d jnz 24 (0xb9064655ad8)
0xb9064655acb 11 488b4e27 REX.W movq rcx,[rsi+0x27]
0xb9064655acf 15 488b492f REX.W movq rcx,[rcx+0x2f]
<==============================
0xb9064655ad3 19 48894c2408 REX.W movq [rsp+0x8],rcx
0xb9064655ad8 24 55 push rbp
0xb9064655ad9 25 4889e5 REX.W movq rbp,rsp
0xb9064655adc 28 56 push rsi
0xb9064655add 29 57 push rdi
0xb9064655ade 30 493ba5c8070000 REX.W cmpq rsp,[r13+0x7c8]
0xb9064655ae5 37 7305 jnc 44 (0xb9064655aec)
0xb9064655ae7 39 e85496fdff call StackCheck (0xb906462f140) ;;
debug: statement 321
being called from 'start' function at:
0xb9064655039 121 48b9815c429bbf380000 REX.W movq
rcx,0x38bf9b425c81 ;; object: 0x38bf9b425c81 <String[3]: foo>
0xb9064655043 131 488b4627 REX.W movq rax,[rsi+0x27]
0xb9064655047 135 e87497fdff call 0xb906462e7c0 ;; debug:
statement 481
;; code:
contextual, LOAD_IC, UNINITIALIZED
0xb906465504c 140 50 push rax
0xb906465504d 141 49ba214170cc66320000 REX.W movq
r10,0x3266cc704121 ;; object: 0x3266cc704121 <undefined>
0xb9064655057 151 4152 push r10
0xb9064655059 153 4c89e2 REX.W movq rdx,r12
0xb906465505c 156 488b7c2408 REX.W movq rdi,[rsp+0x8]
0xb9064655061 161 e85a9dfbff call 0xb906460edc0 ;; code:
CALL_IC, GENERIC
0xb9064655066 166 488b75f8 REX.W movq rsi,[rbp-0x8]
<========================================================
Obviously as long as the frame pointer at foo has not yet been set up to
point to 'start', the 'start' function is missing in the call stack.
--
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
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" 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/d/optout.
