searching for reviewer(njn)
abb03136bfaf: Bug 1468767 - Check result of calling vm_copy() r=njn
Jon Coppeard <jcoppeard@mozilla.com> - Thu, 14 Jun 2018 14:58:45 -0700 - rev 476854
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1468767 - Check result of calling vm_copy() r=njn
035cac21d2b1: Bug 1444765 - Allow setting a pid:<pid> thread filter to capture all threads for a process. r=njn
Kartikaya Gupta <kgupta@mozilla.com> - Thu, 14 Jun 2018 12:41:48 -0400 - rev 476794
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1444765 - Allow setting a pid:<pid> thread filter to capture all threads for a process. r=njn MozReview-Commit-ID: CaMsmEtQ5UY
f2c1f77e2a72: Bug 1464869 - Fix flake8/pep8 issue by hand in memory/ r=njn
Sylvestre Ledru <sledru@mozilla.com> - Fri, 25 May 2018 23:27:02 -0700 - rev 475764
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1464869 - Fix flake8/pep8 issue by hand in memory/ r=njn MozReview-Commit-ID: 8bkhAB4g6rv
ecb4abccd843: Bug 1464869 - Run autopep8 on memory/ r=njn
Sylvestre Ledru <sledru@mozilla.com> - Fri, 25 May 2018 23:16:07 -0700 - rev 475763
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1464869 - Run autopep8 on memory/ r=njn MozReview-Commit-ID: GzFGXZ8WLX5
0df4de6a931f: Bug 1465852. Enforce use of Atomic for static prefs gotten off the main thread. r=njn
Boris Zbarsky <bzbarsky@mit.edu> - Tue, 05 Jun 2018 17:12:16 -0400 - rev 475735
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1465852. Enforce use of Atomic for static prefs gotten off the main thread. r=njn
23e0775d9c9d: Bug 1462784 - Add the list of categories into the profile JSON and bump the version to 11. r=njn
Markus Stange <mstange@themasta.com> - Fri, 25 May 2018 17:28:39 -0400 - rev 475280
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add the list of categories into the profile JSON and bump the version to 11. r=njn MozReview-Commit-ID: 1g4WqsWFFbg
d539f9f0f7ba: Bug 1462784 - Add an IDLE category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 18:15:46 -0400 - rev 475272
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add an IDLE category. r=njn MozReview-Commit-ID: JJ30AhXofBr
a3c9ec2c9d7a: Bug 1462784 - Relabel various other stuff as being OTHER. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:58:43 -0400 - rev 475271
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Relabel various other stuff as being OTHER. r=njn Any more specific work that is happening in these methods will have its own specific category labeling in that specific code. The instances touched in this patch are more on the outside and don't really know what kind of code is going to be running inside. MozReview-Commit-ID: 47NO1DZzkdH
5bc21aa25ea7: Bug 1462784 - Remove the STORAGE category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:55:18 -0400 - rev 475270
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Remove the STORAGE category. r=njn This was used to label IndexedDB work and work in storage/mozStorage*. I don't think this deserves its own category; categories are most useful for the main thread, and most of the time-consuming database-related work happens on helper threads. The main thread pieces are mostly for asynchronicity- coordination and don't usually take up time. This patch labels IndexedDB work as DOM instead (which is maybe debatable) and the rest as OTHER. MozReview-Commit-ID: 3UYhFFbi3Ry
83d77dfa66eb: Bug 1462784 - Add a DOM category and use it for the WebIDL binding stack labels. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:49:55 -0400 - rev 475269
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add a DOM category and use it for the WebIDL binding stack labels. r=njn MozReview-Commit-ID: AevGMqeBvXO
88a612098ee5: Bug 1462784 - Annotate layout-related stacks with the LAYOUT category instead of the GRAPHICS category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:46:59 -0400 - rev 475268
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Annotate layout-related stacks with the LAYOUT category instead of the GRAPHICS category. r=njn MozReview-Commit-ID: 77lvtLaxgEE
3ba0b75a1419: Bug 1462784 - Rename the CSS category to LAYOUT. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:40:52 -0400 - rev 475267
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Rename the CSS category to LAYOUT. r=njn The next changeset is going to move over more annotations that Gecko developers would count as "layout" into the LAYOUT category, and which is currently marked as GRAPHICS. We can add a subcategory for style resolution once we have subcategories, but for now I think it makes more sense to put style resolution into the same bucket as reflow and display list building. MozReview-Commit-ID: 7r9eICVBA1Z
6dc964ee521c: Bug 1462784 - Remove EVENTS category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:36:30 -0400 - rev 475266
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Remove EVENTS category. r=njn Categories are useful to indicate: This much % of time was spent in this category. The EVENTS category isn't a very good match for this. This category is currently only set on labels of functions that handle the processing of an event. But those functions are usually closer to the base of the stack, and the actual CPU work during the processing of an event is usually in another category closer to the top of the stack, e.g. in JS if we're running an event handler, or in LAYOUT if we're hit testing the position of the event. This changeset removes the EVENTS category and replaces all uses of it with the OTHER category. MozReview-Commit-ID: JPm5hQiBkvp
45f1cff50efc: Bug 1462784 - Merge GC and CC categories into one category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:23:33 -0400 - rev 475265
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Merge GC and CC categories into one category. r=njn They're very similar as far as most users of the profiler are concerned, I'd say, and I don't believe it's worth giving them two different colors in the activity graphs. MozReview-Commit-ID: HTqjp56naL3
fbea249b0521: Bug 1462784 - Change the enum ProfilingStackFrame::Category from a bitfield to a regular enum. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:06:13 -0400 - rev 475264
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Change the enum ProfilingStackFrame::Category from a bitfield to a regular enum. r=njn MozReview-Commit-ID: HmDu8Rri5AF
88321efb673b: Bug 1462784 - Add the list of categories into the profile JSON and bump the version to 11. r=njn
Markus Stange <mstange@themasta.com> - Fri, 25 May 2018 17:28:39 -0400 - rev 475259
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add the list of categories into the profile JSON and bump the version to 11. r=njn MozReview-Commit-ID: 1g4WqsWFFbg
e5ad2e525ea9: Bug 1462784 - Add an IDLE category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 18:15:46 -0400 - rev 475251
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add an IDLE category. r=njn MozReview-Commit-ID: JJ30AhXofBr
329645ff1e23: Bug 1462784 - Relabel various other stuff as being OTHER. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:58:43 -0400 - rev 475250
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Relabel various other stuff as being OTHER. r=njn Any more specific work that is happening in these methods will have its own specific category labeling in that specific code. The instances touched in this patch are more on the outside and don't really know what kind of code is going to be running inside. MozReview-Commit-ID: 47NO1DZzkdH
e09c38853172: Bug 1462784 - Remove the STORAGE category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:55:18 -0400 - rev 475249
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Remove the STORAGE category. r=njn This was used to label IndexedDB work and work in storage/mozStorage*. I don't think this deserves its own category; categories are most useful for the main thread, and most of the time-consuming database-related work happens on helper threads. The main thread pieces are mostly for asynchronicity- coordination and don't usually take up time. This patch labels IndexedDB work as DOM instead (which is maybe debatable) and the rest as OTHER. MozReview-Commit-ID: 3UYhFFbi3Ry
0663d1a6d2da: Bug 1462784 - Add a DOM category and use it for the WebIDL binding stack labels. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:49:55 -0400 - rev 475248
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add a DOM category and use it for the WebIDL binding stack labels. r=njn MozReview-Commit-ID: AevGMqeBvXO
106967fc29d2: Bug 1462784 - Annotate layout-related stacks with the LAYOUT category instead of the GRAPHICS category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:46:59 -0400 - rev 475247
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Annotate layout-related stacks with the LAYOUT category instead of the GRAPHICS category. r=njn MozReview-Commit-ID: 77lvtLaxgEE
99b4a433a8e5: Bug 1462784 - Rename the CSS category to LAYOUT. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:40:52 -0400 - rev 475246
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Rename the CSS category to LAYOUT. r=njn The next changeset is going to move over more annotations that Gecko developers would count as "layout" into the LAYOUT category, and which is currently marked as GRAPHICS. We can add a subcategory for style resolution once we have subcategories, but for now I think it makes more sense to put style resolution into the same bucket as reflow and display list building. MozReview-Commit-ID: 7r9eICVBA1Z
1d38a4cf5a4a: Bug 1462784 - Remove EVENTS category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:36:30 -0400 - rev 475245
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Remove EVENTS category. r=njn Categories are useful to indicate: This much % of time was spent in this category. The EVENTS category isn't a very good match for this. This category is currently only set on labels of functions that handle the processing of an event. But those functions are usually closer to the base of the stack, and the actual CPU work during the processing of an event is usually in another category closer to the top of the stack, e.g. in JS if we're running an event handler, or in LAYOUT if we're hit testing the position of the event. This changeset removes the EVENTS category and replaces all uses of it with the OTHER category. MozReview-Commit-ID: JPm5hQiBkvp
692017229de6: Bug 1462784 - Merge GC and CC categories into one category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:23:33 -0400 - rev 475244
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Merge GC and CC categories into one category. r=njn They're very similar as far as most users of the profiler are concerned, I'd say, and I don't believe it's worth giving them two different colors in the activity graphs. MozReview-Commit-ID: HTqjp56naL3
c2911a626671: Bug 1462784 - Change the enum ProfilingStackFrame::Category from a bitfield to a regular enum. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:06:13 -0400 - rev 475243
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Change the enum ProfilingStackFrame::Category from a bitfield to a regular enum. r=njn MozReview-Commit-ID: HmDu8Rri5AF
c8192175f360: Bug 1462784 - Add the list of categories into the profile JSON and bump the version to 11. r=njn
Markus Stange <mstange@themasta.com> - Fri, 25 May 2018 17:28:39 -0400 - rev 474988
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add the list of categories into the profile JSON and bump the version to 11. r=njn MozReview-Commit-ID: 1g4WqsWFFbg
2faf787fbbdf: Bug 1462784 - Add an IDLE category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 18:15:46 -0400 - rev 474980
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add an IDLE category. r=njn MozReview-Commit-ID: JJ30AhXofBr
8f06963c7c6f: Bug 1462784 - Relabel various other stuff as being OTHER. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:58:43 -0400 - rev 474979
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Relabel various other stuff as being OTHER. r=njn Any more specific work that is happening in these methods will have its own specific category labeling in that specific code. The instances touched in this patch are more on the outside and don't really know what kind of code is going to be running inside. MozReview-Commit-ID: 47NO1DZzkdH
036e6f64e224: Bug 1462784 - Remove the STORAGE category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:55:18 -0400 - rev 474978
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Remove the STORAGE category. r=njn This was used to label IndexedDB work and work in storage/mozStorage*. I don't think this deserves its own category; categories are most useful for the main thread, and most of the time-consuming database-related work happens on helper threads. The main thread pieces are mostly for asynchronicity- coordination and don't usually take up time. This patch labels IndexedDB work as DOM instead (which is maybe debatable) and the rest as OTHER. MozReview-Commit-ID: 3UYhFFbi3Ry
e670f156a603: Bug 1462784 - Add a DOM category and use it for the WebIDL binding stack labels. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:49:55 -0400 - rev 474977
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Add a DOM category and use it for the WebIDL binding stack labels. r=njn MozReview-Commit-ID: AevGMqeBvXO
cd39588aece4: Bug 1462784 - Annotate layout-related stacks with the LAYOUT category instead of the GRAPHICS category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:46:59 -0400 - rev 474976
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Annotate layout-related stacks with the LAYOUT category instead of the GRAPHICS category. r=njn MozReview-Commit-ID: 77lvtLaxgEE
2ac65d100fa2: Bug 1462784 - Rename the CSS category to LAYOUT. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:40:52 -0400 - rev 474975
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Rename the CSS category to LAYOUT. r=njn The next changeset is going to move over more annotations that Gecko developers would count as "layout" into the LAYOUT category, and which is currently marked as GRAPHICS. We can add a subcategory for style resolution once we have subcategories, but for now I think it makes more sense to put style resolution into the same bucket as reflow and display list building. MozReview-Commit-ID: 7r9eICVBA1Z
ea05ff70a51d: Bug 1462784 - Remove EVENTS category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:36:30 -0400 - rev 474974
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Remove EVENTS category. r=njn Categories are useful to indicate: This much % of time was spent in this category. The EVENTS category isn't a very good match for this. This category is currently only set on labels of functions that handle the processing of an event. But those functions are usually closer to the base of the stack, and the actual CPU work during the processing of an event is usually in another category closer to the top of the stack, e.g. in JS if we're running an event handler, or in LAYOUT if we're hit testing the position of the event. This changeset removes the EVENTS category and replaces all uses of it with the OTHER category. MozReview-Commit-ID: JPm5hQiBkvp
8a06c0ba42f7: Bug 1462784 - Merge GC and CC categories into one category. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:23:33 -0400 - rev 474973
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Merge GC and CC categories into one category. r=njn They're very similar as far as most users of the profiler are concerned, I'd say, and I don't believe it's worth giving them two different colors in the activity graphs. MozReview-Commit-ID: HTqjp56naL3
52ed9a039ad2: Bug 1462784 - Change the enum ProfilingStackFrame::Category from a bitfield to a regular enum. r=njn
Markus Stange <mstange@themasta.com> - Fri, 18 May 2018 17:06:13 -0400 - rev 474972
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1462784 - Change the enum ProfilingStackFrame::Category from a bitfield to a regular enum. r=njn MozReview-Commit-ID: HmDu8Rri5AF
f0f4de541ce2: bug 1366287 - Part 2.1: Track GMP memory allocation from XPCOM. r=njn
Robin Templeton <robin@igalia.com> - Fri, 11 May 2018 19:42:49 -0700 - rev 474019
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
bug 1366287 - Part 2.1: Track GMP memory allocation from XPCOM. r=njn Based on similar functionality for ICU. Define a GMPReporter class and use its methods for libgmp allocation.
1a3b9492f30d: Bug 1461964 - removed mac 10.6 reference r=njn
Andreea Pavel <apavel> - Sun, 20 May 2018 23:08:00 +0300 - rev 473871
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1461964 - removed mac 10.6 reference r=njn
b1f8ccb26696: Bug 1460838 - Avoid static initializers in mozjemalloc with MSVC. r=njn
Mike Hommey <mh+mozilla@glandium.org> - Thu, 24 May 2018 11:23:10 +0900 - rev 473845
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1460838 - Avoid static initializers in mozjemalloc with MSVC. r=njn
723ce0f95ab2: Bug 1463011 - Constexpr-ify mozilla::NotNull r=njn
Masatoshi Kimura <VYV03354@nifty.ne.jp> - Mon, 21 May 2018 23:03:16 +0900 - rev 473356
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1463011 - Constexpr-ify mozilla::NotNull r=njn MozReview-Commit-ID: EyXmRskjtfU
f556e56e1653: Bug 1458480 - Add a skia memory reporter and report on font cache usage. r=lsalzman, r=njn
Ryan Hunt <rhunt@eqrion.net> - Mon, 14 May 2018 16:47:01 -0500 - rev 473164
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1458480 - Add a skia memory reporter and report on font cache usage. r=lsalzman, r=njn
2e8ec34f785e: Bug 1461677 - Rename compartment to realm in the memory reporting code. r=njn
Jan de Mooij <jdemooij@mozilla.com> - Thu, 17 May 2018 16:15:18 +0200 - rev 472942
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1461677 - Rename compartment to realm in the memory reporting code. r=njn
640682f11718: Bug 1451005 - Add low commit-space event counts to the memory reporter; r=njn
Gabriele Svelto <gsvelto@mozilla.com> - Wed, 16 May 2018 13:58:10 +0200 - rev 472916
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1451005 - Add low commit-space event counts to the memory reporter; r=njn MozReview-Commit-ID: 1jZwxj427tg
ad6107fa1bba: Bug 1451005 - Forward all memory-pressure events to the child processes; r=njn
Gabriele Svelto <gsvelto@mozilla.com> - Sat, 12 May 2018 01:21:13 +0200 - rev 472915
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1451005 - Forward all memory-pressure events to the child processes; r=njn When memory-pressure events were first used in an e10s environment it was to implement memory minimization from about:memory. However when low memory detection was first introduced in Firefox OS an issue arised with this scheme: every process was using a kernel-based low-latency mechanism to detect low memory scenarios and send memory-pressure events; but the main process events were also being forwarded to all child processes causing listeners to be triggered twice. Because of this -no-forward events were introduced and used. Currently however low-memory is detected via polling, so there will always be a significant delay between the beginning of the low-memory scenario and its detection. Because of this there is no value in having content processes poll on their own and it's best to have only the main process do it and then forward the memory-pressure events to all child processes. MozReview-Commit-ID: AMQOsEgECme
dbacc0320046: Bug 1451005 - Introduce a timer-based poller for detecting low-memory scenarios; r=dmajor,njn
Gabriele Svelto <gsvelto@mozilla.com> - Thu, 17 May 2018 14:48:02 +0200 - rev 472914
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1451005 - Introduce a timer-based poller for detecting low-memory scenarios; r=dmajor,njn This patch introduces a new polling mechanism to detect low-memory scenarios. The timer fires at a relatively slow pace and stops whenever the user stops interacting with Firefox to avoid consuming power needlessly. The polling rate is up to 3 orders of magnitude slower than the current tracker and is throttled when memory is running low. It also doesn't suffer from data races that were possible with existing tracker. Contrary to the old available memory tracker which relied on a Windows-specific mechanism, this one could be made to work on other platforms too. The current implementation only supports Windows 64-bit builds though. MozReview-Commit-ID: CFHuTDqjPbL
d5db2927b771: Bug 1461600 - avoid doing memset on ServoSizes since it's not POD. r=njn
Andi-Bogdan Postelnicu <bpostelnicu@mozilla.com> - Tue, 15 May 2018 14:02:11 +0300 - rev 472653
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1461600 - avoid doing memset on ServoSizes since it's not POD. r=njn MozReview-Commit-ID: 4jjLGVDgXWV
589325c8b1a3: Bug 1461555 - Rename PseudoStack to ProfilingStack. r=njn
Markus Stange <mstange@themasta.com> - Tue, 15 May 2018 01:03:11 -0400 - rev 472640
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1461555 - Rename PseudoStack to ProfilingStack. r=njn This also changes many references to the 'pseudo stack' to refer to the 'label stack' instead. The label stack is one of the two stacks that are managed by the profiling stack, the other stack being the JS interpreter stack. MozReview-Commit-ID: Ed0YMMeCBY8
d3ca79e708a5: Bug 1461555 - Rename ProfileEntry to ProfilingStackFrame. r=njn
Markus Stange <mstange@themasta.com> - Tue, 15 May 2018 01:14:03 -0400 - rev 472639
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1461555 - Rename ProfileEntry to ProfilingStackFrame. r=njn The term "entry" is already used for elements in the profile buffer. MozReview-Commit-ID: 1aB22V6veQh
c1e7592188cb: Bug 1431187 - Remove unused function profiler_get_pseudo_stack(). r=njn
Markus Stange <mstange@themasta.com> - Tue, 15 May 2018 00:21:18 -0400 - rev 472638
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1431187 - Remove unused function profiler_get_pseudo_stack(). r=njn MozReview-Commit-ID: KvGTqjex3u3
d6e6fb4dcd70: Bug 1461053 - Treat SP marker frames as their own kind, instead of lumping them together with label frames. r=njn
Markus Stange <mstange@themasta.com> - Mon, 14 May 2018 23:30:32 -0400 - rev 472465
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1461053 - Treat SP marker frames as their own kind, instead of lumping them together with label frames. r=njn MozReview-Commit-ID: 5nQEIgBY4SP
52c0d46e0dc9: Bug 1461053 - Rename Cpp frames to label frames in the ProfilingStack. r=njn
Markus Stange <mstange@themasta.com> - Mon, 14 May 2018 23:21:29 -0400 - rev 472464
Push 9374 by jlund@mozilla.com at 2018-06-18 21:43 +0000
Bug 1461053 - Rename Cpp frames to label frames in the ProfilingStack. r=njn The name Cpp was confusing, because C++ functions are in the native stack, not in the pseudo stack. The pseudo stack only contains frames for manually instrumented code that uses AutoProfilerLabel, and JS frames. MozReview-Commit-ID: 9ptfhREo0qy