https://codereview.chromium.org/264233005/diff/20001/src/execution.cc
File src/execution.cc (right):
https://codereview.chromium.org/264233005/diff/20001/src/execution.cc#newcode735
src/execution.cc:735: ExecutionAccess access(isolate_);
Scope of this lock seems too coarse. Do we really need to hold the lock
when handling debug break? This causes a dead lock in blink when we try
to terminate worker which is running a debug loop on pause:
v8::V8::TerminateExecution is called on the main thread while
ExecutionAccess lock is held on the worker thread. Can we revert this
part of the change and restore previous behavior where the lock is only
held while interrupt flags are accessed?
https://codereview.chromium.org/264233005/
--
--
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.
