summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator.cpp
diff options
context:
space:
mode:
authorYao Chen <yaochen@google.com>2017-11-18 18:56:52 -0800
committerYao Chen <yaochen@google.com>2017-11-18 18:56:52 -0800
commitae6a83a1cd729376fda3a849714b529f9666f4cb (patch)
treee1e81736e5899197076575f5cdcdb8e7ebc23ea2 /tools/aapt2/java/JavaClassGenerator.cpp
parentfe945d189a6b0206b95fbb76155835e0743d487a (diff)
Fix a memory leak in LogEvent
My previous understanding of the liblog api was wrong. Luckily it is caught in time. Also added a memory profiling tool in another CL. Test: statsd_test adb shell dumpsys meminfo adb shell cmd stats meminfo Change-Id: I742af2a38e52e35edf0d4c77ccc35ede7019a73b
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator.cpp')
0 files changed, 0 insertions, 0 deletions