Added a comment to the bug. It allows me to profile for 2 seconds, but
then crashes:
> v8.dll!v8::internal::StandardFrame::IsArgumentsAdaptorFrame(unsigned char
* fp) Line 142 C++
v8.dll!v8::internal::StackFrame::ComputeType(const
v8::internal::StackFrameIteratorBase * iterator,
v8::internal::S
A fix was landed here:
https://chromium.googlesource.com/v8/v8.git/+/d11b44ec69c718a9b3b11872e7638c5675abd02c
does
that resolve your issue?
On Mon, Jan 25, 2016 at 10:47 PM Jim Acquavella
wrote:
> I've filed this as a bug:
> https://bugs.chromium.org/p/v8/issues/detail?id=4705&can=2&q=4705&cols
I've filed this as a bug:
https://bugs.chromium.org/p/v8/issues/detail?id=4705&can=2&q=4705&colspec=ID%20Type%20Status%20Priority%20Owner%20Summary%20HW%20OS%20Component%20Stars
-Jim
--
--
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
---
You r
I just confirmed this happens in my app with the same version as the
shipping Chrome, 4.7.80.25. Not why this is happening for me and not seen
by others. Here's the latest stack crawl:
> v8.dll!v8::base::OS::Abort() Line 825 C++
v8.dll!V8_Fatal(const char * file, int line, const char * format,
Any help would be greatly appreciated. Has anyone from google been able to
confirm the problem? Is it working for others?
On Mon, Dec 14, 2015 at 8:21 AM, Jim Acquavella
wrote:
> Both my debug and optimized builds are crashing while advancing the
> SafeStackFrameIterator
> (via SafeStackFrame
Both my debug and optimized builds are crashing while advancing the
SafeStackFrameIterator
(via SafeStackFrameIterator::Advance()).
On Fri, Dec 11, 2015 at 2:16 PM, Jane Chen wrote:
> This seems only a problem with debug build. Optimized build works fine.
>
>
> On Friday, December 11, 2015 at 2
This seems only a problem with debug build. Optimized build works fine.
On Friday, December 11, 2015 at 2:05:20 PM UTC-8, Jane Chen wrote:
>
> 3.24 crashes too. Same JavaScript query, but different stack:
>
> C stack trace ===
>
> 1: V8_Fatal
> 2: v8::internal:
3.24 crashes too. Same JavaScript query, but different stack:
C stack trace ===
1: V8_Fatal
2: v8::internal::SafeStackFrameIterator::Advance()
3:
v8::internal::SafeStackFrameIterator::SafeStackFrameIterator(v8::internal::Isolate*,
unsigned char*, unsigned c
I am seeing a SIGILL crash too with my embedding app during profiling.
Here's the stack:
Thread [134] (Suspended: Signal 'SIGILL' received. Description: Illegal
instruction.)
40 v8::base::OS::Abort()
/space/projects/v8-git/v8/src/base/platform/platform-posix.cc:229
0x764bcd11
Also, I can provide a binary with instructions on how to reproduce the
problem. I'm using v8 version 4.5.35.
On Wednesday, December 9, 2015 at 4:12:08 PM UTC-8, Jim Acquavella wrote:
>
> I'm seeing this same problem when I start cpu profiling. In my
> case, StackFrameIteratorBase::SingletonFor
I'm seeing this same problem when I start cpu profiling. In my
case, StackFrameIteratorBase::SingletonFor is calling executing this line
with a type of 0x2100.
StackFrame* result = SingletonFor(type);
SingletonFor returns NULL and DCHECK fails.
On Tuesday, December 1, 2015 at 8:30:01 AM
You can find a crashing APK
at https://github.com/slavchev/android-runtime/tree/cpu-profiler-crash/testapk
To produce this APK I took some time and configured the project to use V8
libraries built in debug mode. You can find the project
at https://github.com/slavchev/android-runtime/tree/cpu-pr
Hi Mihail,
The first crash indeed seems to be a corrupt stack, FinishEnqueue doesn't
make any calls that could potentially land at 0x0.
The crash at SafeStackFrameIterator::Advance looks like a real one. The
repro case would really help.
Thanks,
Alex
On Wednesday, December 2, 2015 at 12:14:27
The V8_Fatal implies that you hit one of the stack frames. I guess the fix
added in https://codereview.chromium.org/19775017 was either incomplete or
got broken meanwhile.
If you could provide a repro case, that would be great!
best
-jochen
On Tue, Dec 1, 2015 at 5:30 PM Mihail Slavchev
wrote:
A quick update:
I managed to get bigger call stack on Android 4.4.2 device (the previous
one was Android 5.1.1). Here is the stack
Thread [1] 29168 [core: 0] (Suspended : Signal : SIGILL:Illegal instruction)
v8::base::OS::Abort() at platform-posix.cc:228 0x617ac930
V8_Fatal() at logging.cc:116
Hi Jochen,
Thank you for the quick response. When I run the app under GDB (V8 is built
in debug) I get the following stack:
Thread [1] 14835 [core: 1] (Suspended : Signal : SIGSEGV:Segmentation fault)
0x0
v8::internal::SamplingCircularQueue::FinishEnqueue() at circular-queue-inl.h:55 0xa405ac1
Hi!
can you provide some stack traces, or at least some info on where it
actually crashes?
best
-jochen
On Mon, Nov 30, 2015 at 6:16 PM Mihail Slavchev
wrote:
> Hi guys,
>
> NativeScript developer here. We embed V8 (4.5.103) in android apps and I
> am trying to diagnose an app crash (SIGILL) w
Hi guys,
NativeScript developer here. We embed V8 (4.5.103) in android apps and I am
trying to diagnose an app crash (SIGILL) when the CPU profiler is enabled.
It happens on ARM architecture, both on devices and emulators, and as far
as I observed it happens only in stacks with mixed JavaScript
Hello
I have two questions about the profiler in d8: [3.19.18.4 // Windows 7 //
d8 --prof --log_timer_events test.js]
1) Can I change the sampling period?
The sampling period I get is 16 ms, which isn't very useful. The sampling
period I get in Canary [chrome --no-sandbox --js-flags="--prof
-
Hi all,
I am trying to work with the profiler API but I get an unexpected crash: I
am probably doing something wrong but I can't figure what.. any help or
hints would be appreciated!
>From the main thread I create an isolate and a context. Another thread is
started that enters the created isola
Is there any documentation about how to use the profiler?
--~--~-~--~~~---~--~~
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
-~--~~~~--~~--~--~---
21 matches
Mail list logo
