commit | b7d08df411d00d4578213c7ff3f9278aaf51b7bf | [log] [tgz] |
---|---|---|
author | Maksim Sisov <msisov@igalia.com> | Tue Aug 30 10:31:35 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 30 10:31:35 2022 |
tree | 7a8866013dbe583e3c2facc0f827bba34ed112e6 | |
parent | 7243793c297a0c764bb5001a188ad49ecc49dedb [diff] |
ozone/wayland: fix leak in TestDataSource. Fixes ==65194==ERROR: LeakSanitizer: detected memory leaks Direct leak of 16 byte(s) in 1 object(s) allocated from: #0 0x55c83f57648d in operator new(unsigned long) /b/s/w/ir/cache/builder/src/third_party/llvm/compiler-rt/lib/asan/asan_new_delete.cpp:95:3 #1 0x55c840f862ac in wl::TestDataSource::TestDataSource(wl_resource*) ui/ozone/platform/wayland/test/test_data_source.cc:63:37 #2 0x55c840f85766 in make_unique<wl::TestDataSource, wl_resource *&> buildtools/third_party/libc++/trunk/include/__memory/unique_ptr.h:744:32 #3 0x55c840f85766 in CreateResourceWithImpl<wl::TestDataSource> ui/ozone/platform/wayland/test/server_object.h:81:21 #4 0x55c840f85766 in wl::(anonymous namespace)::CreateDataSource(wl_client*, wl_resource*, unsigned int) ui/ozone/platform/wayland/test/test_data_device_manager.cc:20:3 #5 0x55c84383bda4 in ffi_call_unix64 crtstuff.c SUMMARY: AddressSanitizer: 16 byte(s) leaked in 1 allocation(s). Bug: 1353715 Change-Id: I32cf5508eef51e04b6a2fbd5ff876f618c722f12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3863467 Reviewed-by: Alexander Dunaev <adunaev@igalia.com> Commit-Queue: Maksim Sisov <msisov@igalia.com> Cr-Commit-Position: refs/heads/main@{#1040874}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.