corysanin/tubestation
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Bug 1343396 - Split CycledCollectedJSContext and XPCJSContext into separate context and runtime classes (r=mccr8)

Browse Source 
To run JS in separate cooperative threads, we need to split up per-thread state
from per-runtime state. This patch does that for XPConnect.

MozReview-Commit-ID: 407SlJ7nR6v
This commit is contained in:
Bill McCloskey
2017-02-23 13:23:45 -08:00
parent 1e3951be0d
commit 612db5fd30
29 changed files with 5621 additions and 5041 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
xpcom/base/nsMemoryReporterManager.cpp
View File

@@ -1712,8 +1712,8 @@ nsMemoryReporterManager::StartGettingReports()
s->mAnonymize, parentDMDFile,
s->mFinishReporting, s->mFinishReportingData);
nsTArray<ContentParent*> childWeakRefs;
ContentParent::GetAll(childWeakRefs);
nsTArray<dom::ContentParent*> childWeakRefs;
dom::ContentParent::GetAll(childWeakRefs);
if (!childWeakRefs.IsEmpty()) {
// Request memory reports from child processes. This happens
// after the parent report so that the parent's main thread will