tag | 64492df4a6665a4f03d1d78233c8b00daf92aa65 | |
---|---|---|
tagger | Gergely (sethyx) Szell <sethyx@gmail.com> | Mon Oct 01 01:35:53 2012 +0200 |
object | 69a49e529af9a749e18849ce241ef81a4207a515 |
Build-4
commit | 69a49e529af9a749e18849ce241ef81a4207a515 | [log] [tgz] |
---|---|---|
author | Chih-Hung Chou <robert_ch_chou@acer.com.tw> | Tue Sep 18 10:38:08 2012 -0300 |
committer | Jonathan Steadman <xxwhitehawk@gmail.com> | Wed Sep 26 19:19:44 2012 -0700 |
tree | 776de9e8a2f50d75a55d3f644554a53b3bea1213 | |
parent | f621afad94df46204c25fc2593a19d704d2637f5 [diff] |
fix memory leaking There is a possible memory leaking when lo is allocated but the lo->name is not. In this case, we should free the lo and then return original change I475968bd570a113c9f61f02b974d57d1caaa0236 picked from: https://android-review.googlesource.com/#/c/23450/ Change-Id: I21dd3267fa2521578d93f7b1a7bc2a6726de15ac