5 Коммитов

Автор	SHA1	Сообщение	Дата
Nathan Froyd	9acf5a0c63	Bug 1517276 - thread callbacks through MemoryReportRequestClient; r=mccr8 ... The guts of MemoryReportRequestClient's supporting runnables contain switches on the particular type of process we're running. If you're bringing up a new process type, having to add extra cases for your process type here is a bit onerous. These runnables really shouldn't know anything about the process types that they're running on, either. The easiest thing to do is modify MemoryReportRequestClient::Start to take callbacks for what to do when a report is created and when reporting is finished. Then all process-specific knowledge can be pushed out to the clients themselves, leaving MemoryReportRequestClient and friends process-type agnostic. We could even, at some later date, move this code into xpcom/base/ to sit near nsMemoryReporterManager, where it belongs.	2019-01-02 16:18:13 -05:00
Sylvestre Ledru	265e672179	Bug 1511181 - Reformat everything to the Google coding style r=ehsan a=clang-format ... # ignore-this-changeset --HG-- extra : amend_source : 4d301d3b0b8711c4692392aa76088ba7fd7d1022	2018-11-30 11:46:48 +01:00
David Anderson	694639356f	Remove PMemoryReportRequest. (bug 1321492 part 3, r=erahm) ... --HG-- rename : dom/ipc/PMemoryReportRequest.ipdl => dom/ipc/MemoryReportTypes.ipdlh	2017-01-26 16:35:54 -08:00
David Anderson	b953cadaaa	Remove the MemoryReportRequestChild dependency on ContentChild. (bug 1321492 part 2, r=erahm)	2017-01-26 16:35:53 -08:00
David Anderson	356cc23a9a	Move PMemoryReportRequest classes to a separate source file. (bug 1321492 part 1, r=erahm)	2017-01-26 16:35:53 -08:00