On 2013/06/11 09:56:46, kisg wrote:
We are working on a real fix (although at a lower priority when compared
to
the
daily ports and bug fixes). Were you able to reproduce this issue on your
own
systems with ARM simulator or even regular x86 builds?
Both ia32 and x64 builds hit this (on a multi-core workstation). Sometimes
the
test finishes in less than a second, sometimes it gets killed as timeout
after
60 seconds. Anything between happens as well. I can confirm that generating
lots
of CPU load seems to make it finish faster.
It looks like the problem
is triggered, when all other processes are handled by other cores, and
only
the
2 V8 JS threads are switching back and forth on the same core.
An interesting question is (that we are currently investigating) whether
this
can happen on a multi-core MIPS (or ARM) system,
Since it happens on multi-core x86 systems, probably yes.
and could this issue happen
under real workloads (e.g. inside a real browser or Node.js application).
That would indeed be very interesting to know.
We would like to get this patch in only as a temporary measure, because
this
bug
gets triggered a lot on our build machine(s).
Sure, that's fine, and it's why I LGTM'ed it.
https://codereview.chromium.org/16203005/
--
--
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/groups/opt_out.
