Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(79)

Unified Diff: gin/isolate_holder.cc

Issue 2478813002: When an Isolate is configured to use lockers, foreground tasks need to lock (Closed)
Patch Set: updates Created 4 years, 1 month ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | gin/per_isolate_data.h » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: gin/isolate_holder.cc
diff --git a/gin/isolate_holder.cc b/gin/isolate_holder.cc
index 5252400c13c5572251f72dcfb5b5e86c95ec3685..04449d26ab5657712c8c35d64da65b20424852ea 100644
--- a/gin/isolate_holder.cc
+++ b/gin/isolate_holder.cc
@@ -41,7 +41,7 @@ IsolateHolder::IsolateHolder(AccessMode access_mode)
base::SysInfo::AmountOfVirtualMemory());
params.array_buffer_allocator = allocator;
isolate_ = v8::Isolate::New(params);
- isolate_data_.reset(new PerIsolateData(isolate_, allocator));
+ isolate_data_.reset(new PerIsolateData(isolate_, allocator, access_mode));
isolate_memory_dump_provider_.reset(new V8IsolateMemoryDumpProvider(this));
#if defined(OS_WIN)
{
« no previous file with comments | « no previous file | gin/per_isolate_data.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698