зеркало из https://github.com/mozilla/gecko-dev.git
c1e6abcc0a
Replace it with profiler_is_active() in one place, and simply remove it in the other places. These other places are: - Around the call to profiler_OOP_exit_profile: profiler_OOP_exit_profile itself already checks whether the profiler is running and does nothing if it's not. - When handling the 'profiler-subprocess-gather' notification. This notification is sent by the profiler because it's interested in the profile, so there's little reason to reject it. - In RecvProfile: If the child process sent us a profile, it did so in response to a GatherProfile request, so chances are that we're still interested in that response. These changes may get us a little closer to a state where you can call getProfileDataAsync, stop the profiler before the content process profiles have all come in, and then still receive a response with all the profiles. At the moment, stopping the profiler will abort the profile gathering process, but that seems more like an accident and less like the behavior you'd want. MozReview-Commit-ID: 2tRXC70BztJ --HG-- extra : rebase_source : 3b2f6f51d75d5f0d439e1a815d84164a5a763603 |
||
|---|---|---|
| .. | ||
| bloatview | ||
| coverity | ||
| docs | ||
| fuzzing | ||
| jprof | ||
| leak-gauge | ||
| lint | ||
| memory-profiler | ||
| mercurial | ||
| power | ||
| profiler | ||
| quitter | ||
| rb | ||
| rewriting | ||
| update-packaging | ||
| mach_commands.py | ||
| moz.build | ||