| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
NormalTestClass1* normal_obj1 = new NormalTestClass1;
ASSERT_NE(normal_obj1, nullptr);
EXPECT_NE(leaky_root,
partition_alloc::PartitionRoot::GetRootFromAddress(normal_obj1));
delete normal_obj1;nit: we can use unique_ptr
```
{
auto normal_obj1 = std::make_unique<NormalTestClass1>
ASSERT_NE(normal_obj1, nullptr);
EXPECT_NE(leaky_root,
partition_alloc::PartitionRoot::GetRootFromAddress(normal_obj1));
}
```
Same below.
"malloc/partitions/leaky",maybe `leaked` or `quarantined` or `kept_alive` rather than `leaky` which I feel doesn't fully tell you that things never get freed in here.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +0 |
NormalTestClass1* normal_obj1 = new NormalTestClass1;
ASSERT_NE(normal_obj1, nullptr);
EXPECT_NE(leaky_root,
partition_alloc::PartitionRoot::GetRootFromAddress(normal_obj1));
delete normal_obj1;nit: we can use unique_ptr
```
{
auto normal_obj1 = std::make_unique<NormalTestClass1>
ASSERT_NE(normal_obj1, nullptr);
EXPECT_NE(leaky_root,
partition_alloc::PartitionRoot::GetRootFromAddress(normal_obj1));
}
```Same below.
Done
maybe `leaked` or `quarantined` or `kept_alive` rather than `leaky` which I feel doesn't fully tell you that things never get freed in here.
I see. Done.
I also replaced all `Leaky` with `Leaked` (or `LeakedSecurityObject`).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
LGTM with nits addressed, and the CL description updated to explain more about the purpose of this changeāI don't really know why we need this CL from reading the CL description, but I assume there's a good reason, and that reason should be in the description :)
auto* leaked_secirty_object_allocator =Is this a typo?
std::unique_ptr<NormalTestClass1> normal_obj1(new NormalTestClass1);
ASSERT_NE(normal_obj1, nullptr);Please fix this WARNING reported by ClangTidy: check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.o...
check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.org/extra/clang-tidy/checks/modernize/make-unique.html)
(Note: You can add `Skip-Clang-Tidy-Checks: modernize-make-unique` footer to the CL description to skip the check)
(Lint observed on `linux-clang-tidy-rel`, but not on `android-clang-tidy-rel`)
std::unique_ptr<LeakedTestClass1> leaked_obj1(new LeakedTestClass1);
ASSERT_NE(leaked_obj1, nullptr);Please fix this WARNING reported by ClangTidy: check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.o...
check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.org/extra/clang-tidy/checks/modernize/make-unique.html)
(Note: You can add `Skip-Clang-Tidy-Checks: modernize-make-unique` footer to the CL description to skip the check)
(Lint observed on `android-clang-tidy-rel`, but not on `linux-clang-tidy-rel`)
std::unique_ptr<LeakedTestClass2> leaked_obj2(new LeakedTestClass2);
ASSERT_NE(leaked_obj2, nullptr);Please fix this WARNING reported by ClangTidy: check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.o...
check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.org/extra/clang-tidy/checks/modernize/make-unique.html)
(Note: You can add `Skip-Clang-Tidy-Checks: modernize-make-unique` footer to the CL description to skip the check)
(Lint observed on `android-clang-tidy-rel`, but not on `linux-clang-tidy-rel`)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
LGTM with nits addressed, and the CL description updated to explain more about the purpose of this changeāI don't really know why we need this CL from reading the CL description, but I assume there's a good reason, and that reason should be in the description :)
Done
Thank you for the review.
auto* leaked_secirty_object_allocator =Takashi SakamotoIs this a typo?
Done
std::unique_ptr<NormalTestClass1> normal_obj1(new NormalTestClass1);
ASSERT_NE(normal_obj1, nullptr);Please fix this WARNING reported by ClangTidy: check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.o...
check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.org/extra/clang-tidy/checks/modernize/make-unique.html)
(Note: You can add `Skip-Clang-Tidy-Checks: modernize-make-unique` footer to the CL description to skip the check)
(Lint observed on `linux-clang-tidy-rel`, but not on `android-clang-tidy-rel`)
Done
std::unique_ptr<LeakedTestClass1> leaked_obj1(new LeakedTestClass1);
ASSERT_NE(leaked_obj1, nullptr);Please fix this WARNING reported by ClangTidy: check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.o...
check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.org/extra/clang-tidy/checks/modernize/make-unique.html)
(Note: You can add `Skip-Clang-Tidy-Checks: modernize-make-unique` footer to the CL description to skip the check)
(Lint observed on `android-clang-tidy-rel`, but not on `linux-clang-tidy-rel`)
Done
std::unique_ptr<LeakedTestClass2> leaked_obj2(new LeakedTestClass2);
ASSERT_NE(leaked_obj2, nullptr);Please fix this WARNING reported by ClangTidy: check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.o...
check: modernize-make-unique
use std::make_unique instead (https://clang.llvm.org/extra/clang-tidy/checks/modernize/make-unique.html)
(Note: You can add `Skip-Clang-Tidy-Checks: modernize-make-unique` footer to the CL description to skip the check)
(Lint observed on `android-clang-tidy-rel`, but not on `linux-clang-tidy-rel`)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
5 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: base/trace_event/malloc_dump_provider_unittest.cc
Insertions: 6, Deletions: 3.
The diff is too large to show. Please review the diff.
```
```
The name of the file: base/trace_event/malloc_dump_provider.cc
Insertions: 4, Deletions: 4.
The diff is too large to show. Please review the diff.
```
PA: Add `IntendedLeakSize` to `MallocMemoryDump`
Since leaked security objects are leaked, not really freed, to avoid
heap-use-after-free, they may cause significant memory regressions, and
finally lots of OOM. So we have to monitor how much memory are leaked.
Firstly update memory-infra to gather total size of the leaked memory as
"malloc/partitions/leaked". The size will be reported to UMA in the
later CL.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |