Build failure Google Chrome Mac |
||
Issue descriptionBuild is broken: compile Revision range: chromium 382555 : 382560 Failing builders: Google Chrome Mac: https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Mac Suspecting: https://codereview.chromium.org/1822013002/ per error: trace_event/malloc_dump_provider.cc:11:10: fatal error: 'base/allocator/features.h' file not found #include "base/allocator/features.h" ^ 1 error generated. FAILED with 1: /b/build/goma/gomacc ../native_client/toolchain/mac_x86/pnacl_newlib/bin/pnacl-clang++ -c trace_event/malloc_dump_provider.cc -o ../out/Release/obj/base/base_nacl.gen/pnacl_newlib-pnacl/base_nacl/malloc_dump_provider_eeff7b85.o
,
Mar 22 2016
,
Mar 25 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/fd907216bc422c737219832038e5fc0a5fb66488 commit fd907216bc422c737219832038e5fc0a5fb66488 Author: primiano <primiano@chromium.org> Date: Fri Mar 25 02:13:28 2016 Reland: add dump provider for malloc heap profiler (https://codereview.chromium.org/1675183006/) Reason for reland: the previous CL forgot about the fact that nacl has its own special base target (base_nacl) which is a fork of the real base one. That caused a revert in crrev.com/1822013002 because: - The original CL introduced a dependency from a translation unit in base (malloc_dump_provider.cc) to allocator_features.h, which is a generated header. - The original CL was relying on the fact that there is an existing dependency from base to allocator_features declared in base.gyp. - The original CL forgot about the need of the same dependency from base_nacl. This cl is fixing the latter point. Original breakage: https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Mac/builds/8808 Original issue's description: > tracing: add dump provider for malloc heap profiler > > Now that the allocator shim is landing (the base API landed in > crre.com/1675143004, Linux support in crrev.com/1781573002) we > can use that to implement the malloc heap profiler on top of that. > This CL leverages the new shim API to collect information about > malloc/free and injecting that into the heap profiler, leveraging > the same infrastructure we are already using for PartitionAlloc > and BlinkGC (oilpan). > > Next steps > ---------- > Currently this heap profiler reports also the memory used by the > tracing subsystem itself, which is not desirable. Will come up > with some scoped suppression semantic to bypass the reporting. > > BUG=550886 > TBR=haraken > > Committed: https://crrev.com/14c8b52dac1285bbf23514d05e6109aa7edc427f > Cr-Commit-Position: refs/heads/master@{#382505} BUG=550886, 596873 TBR=ssid@chromium.org,petrcermak@chromium.org,dskiba@google.com,haraken@chromium.org Review URL: https://codereview.chromium.org/1831763003 Cr-Commit-Position: refs/heads/master@{#383225} [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/base/base_nacl.gyp [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/base/trace_event/heap_profiler_allocation_context_tracker.cc [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/base/trace_event/heap_profiler_allocation_context_tracker.h [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/base/trace_event/heap_profiler_allocation_context_tracker_unittest.cc [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/base/trace_event/malloc_dump_provider.cc [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/base/trace_event/malloc_dump_provider.h [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/base/trace_event/trace_log.cc [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/components/tracing/docs/heap_profiler_internals.md [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/third_party/WebKit/Source/platform/PartitionAllocMemoryDumpProvider.cpp [modify] https://crrev.com/fd907216bc422c737219832038e5fc0a5fb66488/third_party/WebKit/Source/platform/heap/BlinkGCMemoryDumpProvider.cpp |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Mar 22 2016